DICOM, Pydicom, GDCM, and Orthanc: A technical tour of what really happens in the heap
Summary: A Cisco Talos white paper presents a case study in which a heap overflow vulnerability in the DICOM file format is used to target an Orthanc server during the image upload process, resulting in an out-of-bounds write. The paper notes that hospitals' PACS systems often automatically ingest files received over the network, so malformed data can directly reach vulnerable decoders.
Bottom line: A PACS server that ingests images automatically over the network turns every upload into a path to an out-of-bounds write in the heap, and the source gives no indication that this requires any action beyond sending a malformed file.
Read the original at Cisco Talos ↗
- Topics
- OT / ICS & Critical Infrastructure
- Related
- Siemens RUGGEDCOM APE1808 Cyber Risks · Nov 12, 2026How to Assess OT Incident Response Preparedness Cyber Risks · Nov 10, 2026Three China-Nexus Espionage Campaigns Linked Through Sparrow Malware Ecosystem Cyber Risks · Nov 10, 2026