# CVE-2006-4507: Memory corruption in n/a

> Local attackers can execute arbitrary code on Sony PSP devices by tricking users into viewing crafted TIFF images in the Photo Viewer.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 31 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gqrr-x6f4-q53v

## What is CVE-2006-4507?

CVE-2006-4507 is a medium-severity memory corruption vulnerability in n/a, published on 31 Aug 2006. 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

Unspecified vulnerability in the TIFF viewer (possibly libTIFF) in the Photo Viewer in the Sony PlaystationPortable (PSP) 2.00 through 2.80 allows local users to execute arbitrary code via crafted TIFF images. NOTE: due to lack of details, it is not clear whether this is related to other issues such as CVE-2006-3464 or CVE-2006-3465.

## Which versions are affected by CVE-2006-4507?

It affects 1 product.


Products: Sony Playstation Portable.

## How do I fix CVE-2006-4507?

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

## Is CVE-2006-4507 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3084](https://insights.sbomify.com/CVE-2005-3084/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4507 and fix it if it is affected.

What it is: CVE-2006-4507 is a medium-severity memory corruption vulnerability in n/a, published on 31 Aug 2006. 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-2006-4507 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-2006-4507/ (Markdown: https://insights.sbomify.com/CVE-2006-4507/index.md)
```

## Sources

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

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