CVE-2017-14348
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 · uneditedLibRaw before 0.18.4 has a heap-based Buffer Overflow in the processCanonCameraInfo function via a crafted file.
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 confidenceLibRaw before 0.18.4 contains a heap-based buffer overflow vulnerability in the processCanonCameraInfo function. When parsing a specially crafted Canon camera file, the library fails to properly validate input sizes before copying data to a heap-allocated buffer, leading to overflow conditions that could enable arbitrary code execution or cause application denial of service.
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<= 0.18.3CVSS 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.0/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 if LibRaw is in useSearch for LibRaw library files (libraw*.so, libraw*.a, libraw.dll, or similar) on the system or within the application directory. Also check application dependencies or package manifests for LibRaw references.Affected if LibRaw library files are found or LibRaw is listed as a dependency
-
Determine the installed LibRaw versionRun version check commands such as 'pkg-config --modversion libraw' or 'dpkg -l | grep libraw' on Linux. On Windows, right-click the LibRaw DLL and view Properties > Details for version info. If using the library in an application, check any version reporting functions or debug output.Affected if The version returned is 0.18.3 or earlier
-
Verify Canon RAW file processing is possibleCheck if the application or system is configured to handle Canon RAW file formats (.CR2, .CRW, .CR3) or if users can upload/import such files. Review file type associations and supported format lists.Affected if Canon RAW file processing is enabled or available in the environment
-
Confirm the vulnerable function is reachableReview application logs or trace functionality to determine if the processCanonCameraInfo code path can be triggered. This function is called when parsing Canon camera metadata in RAW files.Affected if The application processes Canon RAW files and the LibRaw version is 0.18.3 or earlier
A system is affected if it runs LibRaw version 0.18.3 or earlier and processes Canon RAW files using the vulnerable processCanonCameraInfo 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 LibRaw version 0.18.4 or later. Applications using LibRaw should rebuild against the patched version and ensure that untrusted Canon RAW files are not processed with vulnerable library versions.
- 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-2017-14348 — 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-14348 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