Veille CVE

Recherche « J4Care dcm4chee-arc-light »

6 CVE

  1. CVE-2026-97851 9.1 Critique

    J4Care dcm4chee-arc-light

    The storage status-change REST service allows location records still associated with DICOM instances to be changed to deletion-related states. Changing a location to TO_DELETE causes PurgeStorageScheduler to delete the referenced object from storage even though the corresponding instance record remains in the database.

  2. CVE-2026-107621 7.5 Élevée

    J4Care dcm4chee-arc-light

    JPEGParser can enter an infinite loop while parsing a specially crafted or truncated stream.

  3. CVE-2026-105667 7.5 Élevée

    J4Care dcm4chee-arc-light

    In the default configuration, the HL7 listener accepts ADT^A40 patient-merge messages without authenticating the sending application. A remote sender can reassign studies and related workflow records from one patient identity to another. The archive's unmerge does not reverse this.

  4. CVE-2026-105279 9.1 Critique

    J4Care dcm4chee-arc-light

    In the default configuration, the archive accepts DICOM associations from an unregistered calling AE. A remote peer can use C-FIND and C-GET to enumerate and retrieve patient information and medical images. It can also use C-STORE to file fabricated study content under an existing patient identity.

  5. CVE-2026-105273 7.5 Élevée

    J4Care dcm4chee-arc-light

    MP4Parser does not adequately validate MP4 box sizes. A malformed box can cause parsing to make no forward progress and repeatedly process the same input.

  6. CVE-2026-101021 7.5 Élevée

    J4Care dcm4chee-arc-light

    MultipartInputStream performs inefficient boundary matching and unnecessary buffer copying. Crafted multipart input can force excessive boundary comparisons and repeated copying.