# CVE-2005-0406: Information disclosure in n/a

> Attackers can recover sensitive visual data from EXIF thumbnails in modified JPEG images due to a design flaw in image processing software.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0406, GHSA-578w-c3rg-xx4q

## What is CVE-2005-0406?

CVE-2005-0406 is a medium-severity vulnerability in n/a, published on 16 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A design flaw in image processing software that modifies JPEG images might not modify the original EXIF thumbnail, which could lead to an information leak of potentially sensitive visual information that had been removed from the main JPEG image.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2005-0406?

It affects 1 product.


Products: Image Processing Project Image Processing.

## How do I fix CVE-2005-0406?

No fix has been published for CVE-2005-0406 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-0406 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0406 and fix it if it is affected.

What it is: CVE-2005-0406 is a medium-severity vulnerability in n/a, published on 16 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0406 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-2005-0406/ (Markdown: https://insights.sbomify.com/CVE-2005-0406/index.md)
```

## Sources

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

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