CVE-2019-5091
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 denial-of-service 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 infinite loop, resulting in a denial of service. 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 confidenceA denial-of-service vulnerability exists in the DICOM packet parsing functionality of LEADTOOLS libltdic.so version 20.0.2019.3.15. A specially crafted DICOM packet can cause an infinite loop in the parser, consuming CPU resources and rendering the service unresponsive. The CVSS 7.5 score indicates high severity due to the availability impact.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the LEADTOOLS DICOM librarySearch for libltdic.so in your application directories, commonly found in /opt/, /usr/lib/, or within the application's lib folder. Use: find / -name 'libltdic.so' 2>/dev/nullAffected if libltdic.so is present in your environment
-
Verify the library versionOnce located, check the version using: ls -la /path/to/libltdic.so or check the file metadata. The affected version is 20.0.2019.3.15 specificallyAffected if The installed version matches 20.0.2019.3.15 exactly
-
Confirm DICOM parsing is in useReview application configuration and logs to determine if DICOM file processing or DICOM network services are enabled. Check for .dcm file handling or DICOM listener configurations in your applicationAffected if DICOM parsing functionality is actively used or configured in your application
-
Monitor for DoS symptomsIf LEADTOOLS with DICOM support is in use, monitor for sudden CPU spikes and service unresponsiveness. Use 'top' or 'htop' to observe process CPU usage and check if a single thread consumes 100% CPU continuouslyAffected if Experience unexplained 100% CPU usage by processes handling DICOM data without recovery
You are affected if libltdic.so version 20.0.2019.3.15 is installed and your application processes DICOM packets, as this specific version contains the vulnerable infinite loop in DICOM packet parsing.
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 when available. Until then, consider network-level filtering of untrusted DICOM packets or disabling the affected parsing functionality if possible. Implement request rate limiting to mitigate repeated exploitation attempts.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5091 — 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-5091 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