# CVE-2009-3895: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a malicious EXIF image processed by the libexif library.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** ALPINE-CVE-2009-3895, DEBIAN-CVE-2009-3895, GHSA-v836-r6h4-7334

## What is CVE-2009-3895?

CVE-2009-3895 is a medium-severity memory corruption vulnerability in n/a, published on 20 Nov 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the exif_entry_fix function (aka the tag fixup routine) in libexif/exif-entry.c in libexif 0.6.18 allows remote attackers to cause a denial of service or possibly execute arbitrary code via an invalid EXIF image.  NOTE: some of these details are obtained from third party information.

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

## Which versions are affected by CVE-2009-3895?

It affects 1 product.


Products: Libexif Project Libexif.

## How do I fix CVE-2009-3895?

Upgrade to a fixed version.

## Is CVE-2009-3895 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7544](https://insights.sbomify.com/CVE-2017-7544/): Information disclosure in libexif (critical 9.1)
- [CVE-2018-20030](https://insights.sbomify.com/CVE-2018-20030/): Denial of service in libexif (high 7.5)
- [CVE-2012-2814](https://insights.sbomify.com/CVE-2012-2814/): Memory corruption in n/a (high 7.5)
- [CVE-2012-2840](https://insights.sbomify.com/CVE-2012-2840/): Integer overflow in n/a (high 7.5)
- [CVE-2012-2841](https://insights.sbomify.com/CVE-2012-2841/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3895 and fix it if it is affected.

What it is: CVE-2009-3895 is a medium-severity memory corruption vulnerability in n/a, published on 20 Nov 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-3895 in the wild and no public exploit code.

Affected product: n/a. 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-2009-3895/ (Markdown: https://insights.sbomify.com/CVE-2009-3895/index.md)
```

## Sources

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

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