CVE-2019-5092
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 heap out of bounds write vulnerability exists in the UI tag parsing functionality of the DICOM image format of LEADTOOLS 20.0.2019.3.15. A specially crafted DICOM image can cause an offset beyond the bounds of a heap allocation to be written, potentially resulting in code execution. An attacker can specially craft a DICOM image 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 confidenceHeap out-of-bounds write vulnerability in LEADTOOLS DICOM parser's UI tag parsing functionality. A specially crafted DICOM image with an invalid offset in the UI tag causes writing beyond the bounds of a heap allocation, potentially leading to 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify LEADTOOLS installationSearch for Leadtools DLLs or libraries in your application dependencies, installation directory, or used packages (e.g., Leadtools.dll, Leadtools.Dicom.dll). On Windows, check Program Files or the application's bin folder.Affected if LEADTOOLS library files are present in your environment
-
Verify LEADTOOLS versionRight-click on Leadtools.dll, select Properties, then Details tab to view File Version. Alternatively, check the assembly version programmatically or via package manager if using NuGet.Affected if The version shown is exactly 20.0.2019.3.15
-
Confirm DICOM parsing is in useReview your application code or configuration to determine if DICOM file parsing functionality (Leadtools.Dicom namespace or UI tag parsing) is actively used or loaded at runtime.Affected if Your application loads or uses the DICOM parser component to process DICOM images
-
Check for untrusted DICOM input handlingAudit your data flow for DICOM file ingestion. Identify if DICOM files from external/untrusted sources are processed without additional validation. Look for file upload paths or network receivers handling .dcm files.Affected if Your system processes DICOM files from untrusted or external sources without sanitization
You are affected if LEADTOOLS version 20.0.2019.3.15 is installed and your environment processes DICOM files using the UI tag parsing functionality.
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 vendor patch from LEADTOOLS. Until patch is available, sanitize or reject DICOM files from untrusted sources, and implement additional validation on UI tag parsing to verify offsets remain within allocation boundaries.
- Consultation4.0 h
- Implementation6.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5092 — 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-5092 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