Application crash via invalid RLE stripe size
Published Feb 18, 2025 · Updated Nov 3, 2025
Null pointer dereference in DCMTK 3.6.9 allows attackers to crash DICOM-processing applications via a crafted DICOM file. DcmRLECodecDecoder::decode trusts an RLE header stripe size and passes an overlong input length to decompress instead of limiting it to the remaining fragment. An application must decode the invalid image; the documented consequence is a service interrupt, with no reported confidentiality or integrity impact.
Summary
What happened
Null pointer dereference in DCMTK 3.6.9 allows attackers to crash DICOM-processing applications via a crafted DICOM file. DcmRLECodecDecoder::decode trusts an RLE header stripe size and passes an overlong input length to decompress instead of limiting it to the remaining fragment. An application must decode the invalid image; the documented consequence is a service interrupt, with no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2025-25475
- Published
- Feb 18, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 18, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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