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

> Local attackers can cause denial of service or delete arbitrary files via symlink attacks due to predictable temporary directory names in Audacity.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-6061, GHSA-3pxp-pwrp-2w6f, openSUSE-SU-2024:10639-1

## What is CVE-2007-6061?

CVE-2007-6061 is a medium-severity path traversal vulnerability in n/a, published on 20 Nov 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Audacity 1.3.2 creates a temporary directory with a predictable name without checking for previous existence of that directory, which allows local users to cause a denial of service (recording deadlock) by creating the directory before Audacity is run.  NOTE: this issue can be leveraged to delete arbitrary files or directories via a symlink attack.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `audacity` | openSUSE:Tumbleweed | All versions | 3.0.4-1.2 |

Products: Audacityteam Audacity.

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

Upgrade to a fixed version.

## Is CVE-2007-6061 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0490](https://insights.sbomify.com/CVE-2009-0490/): Memory corruption in n/a (critical 9.3)
- [CVE-2017-1000010](https://insights.sbomify.com/CVE-2017-1000010/): Other in n/a (high 7.8)
- [CVE-2016-2540](https://insights.sbomify.com/CVE-2016-2540/): Memory corruption in n/a (medium 5.5)
- [CVE-2016-2541](https://insights.sbomify.com/CVE-2016-2541/): Memory corruption in n/a (medium 5.5)
- [CVE-2020-11867](https://insights.sbomify.com/CVE-2020-11867/): Information disclosure in n/a (low 3.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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