CVE-2017-13735
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 · uneditedThere is a floating point exception in the kodak_radc_load_raw function in dcraw_common.cpp in LibRaw 0.18.2. It will lead to a remote denial of service attack.
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 floating point exception (likely division by zero or arithmetic overflow) occurs in the kodak_radc_load_raw function in dcraw_common.cpp in LibRaw 0.18.2 when processing specially crafted image files, causing the application to crash and resulting in a remote 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.2CVSS 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.0/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.
-
Identify LibRaw installation and versionRun 'pkg-config --modversion libraw' or check your package manager for the installed LibRaw version. If built from source, check the version in the source code or build logs.Affected if The installed version is exactly 0.18.2
-
Locate the vulnerable dcraw_common.cpp componentSearch for the dcraw_common.cpp file in your LibRaw installation directory, typically found in the library source path under src/ or libraw/.Affected if The file exists and is from LibRaw version 0.18.2
-
Verify kodak_radc_load_raw function presenceInspect dcraw_common.cpp and search for the function 'kodak_radc_load_raw' to confirm the vulnerable code path exists in your installation.Affected if The kodak_radc_load_raw function is present in the codebase
-
Check for Kodak RADC image processing activityReview any application logs, image processing scripts, or tools that use LibRaw to process Kodak RAW camera images (.radc extension), as this function handles that format.Affected if Your applications process Kodak RADC format images using this LibRaw installation
-
Look for crash or floating point exception evidenceCheck system logs, application error logs, or core dumps for floating point exceptions (FPE) or division by zero errors occurring during image processing.Affected if Logs show FPE or arithmetic overflow errors when processing image files
You are affected if LibRaw version 0.18.2 is installed AND your environment processes Kodak RADC format image files, which triggers the vulnerable kodak_radc_load_raw function causing a crash.
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 LibRaw to a patched version when available; avoid processing untrusted or potentially malicious image files until the vulnerability is remediated.
- 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-13735 — 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-13735 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