Lucene search
+L

11 matches found

Cvelist
Cvelist
•added 2026/10/16 2:32 p.m.•7 views

CVE-2026-105667 J4Care dcm4che Missing Authentication for Critical Function

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...

8.7CVSS
SaveExploits0References2
CVE
CVE
•added 2026/10/16 2:32 p.m.•10 views

CVE-2026-105667

The J4Care dcm4che system contains a vulnerability where the HL7 listener accepts ADT^A40 patient-merge messages without authenticating the sending application in the default configuration. This lack of authentication allows a remote sender to reassign studies and related workflow records from on...

8.7CVSS5.9AI score
SaveExploits0References2
CVE
CVE
•added 2026/10/16 2:30 p.m.•10 views

CVE-2026-105279

The J4Care dcm4che archive is vulnerable to a missing authentication flaw (CWE-306) in its default configuration. The system incorrectly accepts DICOM associations from unregistered calling AEs, allowing a remote peer to perform unauthorized actions. Specifically, an attacker can use C-FIND and C...

9.3CVSS5.8AI score
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/16 2:30 p.m.•7 views

CVE-2026-105279 J4Care dcm4che Missing Authentication for Critical Function

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 identit...

9.3CVSS
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/16 2:28 p.m.•11 views

CVE-2026-101021 J4Care dcm4che Inefficient Algorithmic Complexity

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

8.7CVSS
SaveExploits0References2
CVE
CVE
•added 2026/10/16 2:28 p.m.•8 views

CVE-2026-101021

The J4Care dcm4che software is vulnerable to an Inefficient Algorithmic Complexity flaw (CWE-407) within the MultipartInputStream component. The root cause is that the component performs inefficient boundary matching and unnecessary buffer copying. An attacker can provide crafted multipart input ...

8.7CVSS6AI score
SaveExploits0References2
CVE
CVE
•added 2026/10/16 2:21 p.m.•12 views

CVE-2026-105273

The J4Care dcm4che software contains a vulnerability where the MP4Parser fails to adequately validate MP4 box sizes . A malformed box can cause the parser to make no forward progress, resulting in a loop with an unreachable exit condition (CWE-835). This flaw can lead to high availability impact ...

8.7CVSS5.8AI score
SaveExploits0References2
CVE
CVE
•added 2026/10/16 2:19 p.m.•10 views

CVE-2026-107621

The J4Care dcm4che software is vulnerable to a Loop with Unreachable Exit Condition (CWE-835) within the JPEGParser component. An attacker can trigger an infinite loop by providing a specially crafted or truncated stream. This vulnerability results in a High impact on availability , as it can lea...

8.7CVSS5.8AI score
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/16 2:19 p.m.•14 views

CVE-2026-107621 J4Care dcm4che Loop with Unreachable Exit Condition

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

8.7CVSS
SaveExploits0References2
CVE
CVE
•added 2026/10/16 2:16 p.m.•15 views

CVE-2026-97851

The J4Care dcm4che software contains a Missing Authorization vulnerability (CWE-862) within its storage status-change REST service . An attacker can modify location records associated with DICOM instances to a TO_DELETE state. This action triggers the PurgeStorageScheduler to delete the reference...

9.1CVSS5.8AI score
SaveExploits0References2
Cvelist
Cvelist
•added 2026/10/16 2:16 p.m.•15 views

CVE-2026-97851 J4Care dcm4che 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 TODELETE causes PurgeStorageScheduler to delete the referenced object from storage even though the corresponding instance record...

9.1CVSS
SaveExploits0References2
Rows per page
Query Builder