Information leak via unchecked JPEG scanline bounds
Published Dec 16, 2025 · Updated Dec 16, 2025
Out-of-bounds read in GDCM 3.024 allows local users to disclose process memory by supplying a crafted DICOM file for JPEG compression. JPEGBITSCodec::InternalCode ignores the input length when deriving scanline pointers, and null_convert reads using file-controlled dimensions and component counts. The file must be processed by a local GDCM consumer; the read can disclose adjacent memory or crash the process.
Summary
What happened
Out-of-bounds read in GDCM 3.024 allows local users to disclose process memory by supplying a crafted DICOM file for JPEG compression. JPEGBITSCodec::InternalCode ignores the input length when deriving scanline pointers, and null_convert reads using file-controlled dimensions and component counts. The file must be processed by a local GDCM consumer; the read can disclose adjacent memory or crash the process.
The record
- CVE
- CVE-2025-53619
- Published
- Dec 16, 2025
- Updated
- Dec 16, 2025
- Vendor
- Grassroots DICOM
- Product
- GDCM
- Classifications
- CWE-125, CWE-119
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2025CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.024
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo