CVE-2017-2812
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 · uneditedA code execution vulnerability exists in the kdu_buffered_expand function of the Kakadu SDK 7.9. A specially crafted JPEG 2000 file can be read by the program and can lead to an out of bounds write causing an exploitable condition to arise.
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 code execution vulnerability exists in the kdu_buffered_expand function of Kakadu SDK 7.9. When parsing a specially crafted JPEG 2000 file, the function performs an out-of-bounds write due to insufficient bounds checking, allowing an attacker to overwrite memory and potentially execute arbitrary code.
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= 7.9CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 if Kakadu SDK is installedSearch for Kakadu SDK binaries or libraries on the system. Common locations include /usr/lib/, /usr/local/lib/, or application-specific directories. Look for files named libkdu*.so (Linux) or kdu*.dll (Windows).Affected if Kakadu SDK libraries are present on the system
-
Determine the installed Kakadu SDK versionCheck the version of the Kakadu SDK library file. This may be visible in the filename, embedded in the binary metadata, or obtainable via the application's own version reporting if available. Compare against the affected version: 7.9.Affected if The installed version is exactly 7.9
-
Identify applications using Kakadu SDKReview applications or services that depend on Kakadu SDK by checking linked libraries (ldd on Linux, dependency walker on Windows) or reviewing application documentation. Determine if JPEG 2000 image processing is a feature.Affected if An application links against Kakadu SDK and processes JPEG 2000 images
-
Inspect JPEG 2000 processing workflowsReview configuration files, file type associations, or processing pipelines that handle .jp2, .j2k, .jpx, or .jpm files. Determine whether untrusted JPEG 2000 files can be submitted to the application.Affected if The application accepts and processes JPEG 2000 files from external or untrusted sources
You are affected if Kakadu SDK version 7.9 is installed AND your system or application parses JPEG 2000 files using the kdu_buffered_expand function.
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 dataUpgrade to a patched version of Kakadu SDK, or implement strict validation of JPEG 2000 file structures before processing to prevent malformed files from reaching the vulnerable function.
- Consultation4.0 h
- Implementation8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2812 — 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-2017-2812 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