# CVE-2007-4460: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks on temporary files during ID3 tag rendering in id3lib.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 21 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4460, DSA-1365-1, DSA-1365-2, DSA-1365-3, GHSA-9j28-rgm8-rqw2, openSUSE-SU-2024:10082-1

## What is CVE-2007-4460?

CVE-2007-4460 is a high-severity path traversal vulnerability in n/a, published on 21 Aug 2007. 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

The RenderV2ToFile function in tag_file.cpp in id3lib (aka libid3) 3.8.3 allows local users to overwrite arbitrary files via a symlink attack on a temporary file whose name is constructed from the name of a file being tagged.

## Which versions are affected by CVE-2007-4460?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `id3lib` | openSUSE:Tumbleweed | All versions | 3.8.3-266.5 |

Products: Id3lib Id3lib.

## How do I fix CVE-2007-4460?

Apply the vendor's patch.

## Is CVE-2007-4460 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4460 and fix it if it is affected.

What it is: CVE-2007-4460 is a high-severity path traversal vulnerability in n/a, published on 21 Aug 2007. 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-2007-4460 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-2007-4460/ (Markdown: https://insights.sbomify.com/CVE-2007-4460/index.md)
```

## Sources

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

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