# CVE-2017-6887: Memory corruption in LibRaw

> A boundary error in LibRaw allows attackers to cause memory corruption and potentially execute code via a crafted KDC file.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-6887, DEBIAN-CVE-2017-6887, GHSA-3g72-9f6h-w6pf, UBUNTU-CVE-2017-6887

## What is CVE-2017-6887?

CVE-2017-6887 is a high-severity memory corruption vulnerability in Libraw Libraw, published on 16 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A boundary error within the "parse_tiff_ifd()" function (internal/dcraw_common.cpp) in LibRaw versions before 0.18.2 can be exploited to cause a memory corruption via e.g. a specially crafted KDC file with model set to "DSLR-A100" and containing multiple sequences of 0x100 and 0x14A TAGs.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-6887?

It affects 1 product.


Products: Libraw Libraw.

## How do I fix CVE-2017-6887?

Upgrade to a fixed version.

## Is CVE-2017-6887 being exploited?

There is no known exploitation of CVE-2017-6887 in the wild and no public exploit code.

## Other vulnerabilities in Libraw Libraw

- [CVE-2026-20889](https://insights.sbomify.com/CVE-2026-20889/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2026-20911](https://insights.sbomify.com/CVE-2026-20911/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2026-21413](https://insights.sbomify.com/CVE-2026-21413/): Memory corruption in LibRaw (critical 9.8)
- [CVE-2015-8366](https://insights.sbomify.com/CVE-2015-8366/): Integer overflow in n/a (critical 9.8)
- [CVE-2015-8367](https://insights.sbomify.com/CVE-2015-8367/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6887 and fix it if it is affected.

What it is: CVE-2017-6887 is a high-severity memory corruption vulnerability in Libraw Libraw, published on 16 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-6887 in the wild and no public exploit code.

Affected product: Libraw Libraw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6887/ (Markdown: https://insights.sbomify.com/CVE-2017-6887/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6887
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6887
- OSV: https://osv.dev/vulnerability/CVE-2017-6887

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6887/
Summaries are generated and may contain mistakes; the official description above is the record.