J4Care vulnerabilities
We track 5 vulnerabilities in J4Care products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on October 16, 2026.
Latest J4Care vulnerabilities
- 9.1 Critical severity
dcm4chee-arc-light: Missing Authorization
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 thoug
- 7.5 High severity
dcm4chee-arc-light: Missing Authentication for Critical Functionality
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
- 9.1 Critical severity
dcm4chee-arc-light: Missing Authentication for Critical Functionality
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 cont
- 7.5 High severity
dcm4chee-arc-light: Loop with Unreachable Exit Condition
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.
- 7.5 High severity
dcm4chee-arc-light: Inefficient Algorithmic Complexity
MultipartInputStream performs inefficient boundary matching and unnecessary buffer copying. Crafted multipart input can force excessive boundary comparisons and repeated copying.