CVE-2019-5154
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 overflow vulnerability exists in the JPEG2000 parsing functionality of LEADTOOLS 20.0.2019.3.15. A specially crafted J2K image file can cause an out of bounds write of a null byte in a heap buffer, potentially resulting in code execution. An attack can specially craft a J2K 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 confidenceA heap overflow vulnerability exists in LEADTOOLS 20.0.2019.3.15's JPEG2000 (J2K) image parsing functionality. Specially crafted J2K files can trigger an out-of-bounds write of a null byte to heap memory, potentially allowing 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
- 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.
-
Locate LEADTOOLS DLL filesSearch for DLL files matching 'Leadtools*.dll' in the application installation directory and subdirectories. Common paths include the bin folder, system directories, or the application's root directory.Affected if Any Leadtools DLL with version 20.0.2019.3.15 is found on the system
-
Verify the exact LEADTOOLS versionRight-click each Leadtools DLL, select Properties, then click the Details tab. Compare the 'File version' or 'Product version' field to 20.0.2019.3.15.Affected if The installed version is exactly 20.0.2019.3.15
-
Confirm JPEG2000/J2K parsing component existsSearch for the J2K-related DLL component such as Leadtools.J2k.dll, Leadtools.Codecs.J2k.dll, or similar JPEG2000-specific DLLs in the LEADTOOLS installation directory.Affected if A J2K/JPEG2000 parsing DLL from the Leadtools library is present alongside version 20.0.2019.3.15
-
Identify J2K file processing in the applicationReview application logs, configuration files, or code references that indicate the application accepts or processes .j2k, .jp2, or .jpx file formats using LEADTOOLS imaging functions.Affected if The application is configured to parse, decode, or render JPEG2000 (J2K/JP2/JPX) image files using the affected LEADTOOLS version
You are affected if LEADTOOLS version 20.0.2019.3.15 is installed AND your application or system processes JPEG2000/J2K image files using the LEADTOOLS library.
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 LEADTOOLS to the vendor-provided patched version. If a patch is unavailable, consider disabling JPEG2000/J2K parsing in the application or implementing input validation to reject untrusted J2K files until a fix is available.
- Consultation4.0 h
- Implementation4.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5154 — 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-5154 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