CVE-2019-5090
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn exploitable information disclosure vulnerability exists in the DICOM packet-parsing functionality of LEADTOOLS libltdic.so, version 20.0.2019.3.15. A specially crafted packet can cause an out-of-bounds read, resulting in information disclosure. An attacker can send a packet to trigger this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn out-of-bounds read vulnerability exists in the DICOM packet-parsing functionality of LEADTOOLS libltdic.so version 20.0.2019.3.15. Attackers can send specially crafted DICOM packets to trigger the vulnerability, causing the parser to read memory outside allocated buffer boundaries and leak sensitive information to the attacker.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 20.0.2019.3.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the LEADTOOLS DICOM library fileSearch the system for libltdic.so using 'find / -name "libltdic.so" 2>/dev/null' or check common library directories such as /usr/lib, /opt, or application-specific pathsAffected if The library file libltdic.so is present on the system
-
Determine the installed version of libltdic.soUse 'file libltdic.so' to confirm the binary, then check for version information using 'strings libltdic.so | grep -i "20.0.2019"' or check version metadata in the application that uses this libraryAffected if The version string matches exactly 20.0.2019.3.15
-
Verify if DICOM services are running or accessibleCheck for running processes that handle DICOM traffic using 'ps aux | grep -i dicom' or examine listening network ports with 'netstat -tuln' or 'ss -tuln' for DICOM service ports (commonly 104, 11112, or custom ports)Affected if A DICOM service is running and accepting network connections
-
Confirm DICOM packet parsing is in active useReview application logs, configuration files, or network traffic captures to determine if the system is receiving and processing incoming DICOM packets from external sourcesAffected if The system processes DICOM packets from untrusted network sources
You are affected if libltdic.so version 20.0.2019.3.15 is installed and DICOM packet parsing functionality is exposed to untrusted network traffic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch for CVE-2019-5090 to libltdic.so. Until then, restrict network exposure of DICOM services and validate incoming DICOM packets at network boundaries.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data