Skip to content
NewA calmer, faster ZeroHour

GDCM <= 3.2.7: six memory-safety and denial-of-service vulnerabilities, no CVE

oss-security ()1 · 1 read
AI summary · glm-5.3-flashSummaries by Vani AI

Six memory-safety and denial-of-service flaws disclosed in the GDCM DICOM parsing library, affecting versions through 3.2.7.

Researcher Abhinav Agarwal disclosed six vulnerabilities in GDCM (Grassroots DICOM), an open-source C++ library for parsing and processing DICOM files. All six were confirmed against GDCM 3.2.6 using AddressSanitizer and UndefinedBehaviorSanitizer, and source review found the vulnerable patterns through version 3.2.7 and the upstream master snapshot. Potential impacts include heap corruption, process-memory disclosure, stack exhaustion, and process termination in applications parsing untrusted DICOM files. No CVE identifiers have been assigned at the time of disclosure.

Key facts
  • Confirmed via AddressSanitizer and UndefinedBehaviorSanitizer against GDCM 3.2.6
  • Vulnerable patterns persist through version 3.2.7 and upstream master
  • Impacts include heap corruption, memory disclosure, and stack exhaustion
  • No CVE identifiers assigned at time of disclosure
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

Posted by Abhinav Agarwal on Sep 09 I am disclosing six vulnerabilities in GDCM (Grassroots DICOM), an open-source C++ library for parsing and processing DICOM files. I confirmed all six against GDCM 3. 2.

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.