CVE-2019-5093
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 code execution vulnerability exists in the DICOM network response functionality of LEADTOOLS libltdic.so version 20.0.2019.3.15. A specially crafted packet can cause an integer overflow, resulting in heap corruption. 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 · high confidenceA critical integer overflow vulnerability exists in the DICOM network response handler of LEADTOOLS libltdic.so version 20.0.2019.3.15. Attackers can send specially crafted network packets to trigger an integer overflow that leads to heap corruption and remote code execution.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 libltdic.so on the systemSearch for the library file using 'find / -name libltdic.so 2>/dev/null' or 'locate libltdic.so' if the database is updated. Check typical installation paths such as /usr/lib/, /opt/, or application-specific directories.Affected if The library file exists and is located in a path used by your DICOM applications.
-
Determine the exact version of libltdic.soUse 'strings libltdic.so | grep -i version' or inspect file metadata with 'file libltdic.so'. If the library is linked to an application, check the application's about dialog or version information for the LEADTOOLS component.Affected if The version string reports exactly 20.0.2019.3.15.
-
Identify if DICOM network services are runningCheck for listening ports associated with DICOM services using 'netstat -tulpn | grep -E "104|11112"' or 'ss -tulpn'. Review your application documentation to identify which ports the DICOM listener uses.Affected if A DICOM network service is listening and accessible on the system.
-
Verify the application uses the vulnerable libraryCheck running processes for library dependency using 'ldd <application_binary>' or 'ps aux | grep <dicom_process>'. Alternatively, review the application's module or plugin configuration.Affected if The application or service is dynamically linked to libltdic.so version 20.0.2019.3.15.
You are affected if libltdic.so version 20.0.2019.3.15 is present AND a DICOM network service using that library is running and accessible.
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 dataUpdate libltdic.so to a patched version that addresses the integer overflow vulnerability. If no update is available, consider network segmentation to limit exposure to untrusted DICOM connections.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5093 — 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-5093 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