# CVE-2006-2021: Path traversal in n/a

> Remote attackers can read arbitrary audio files and determine file existence via path traversal in the Asterisk@Home web interface.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jr9f-93rq-w256

## What is CVE-2006-2021?

CVE-2006-2021 is a medium-severity path traversal vulnerability in n/a, published on 25 Apr 2006. It can be exploited over the network, with no action from the victim.

### Official description

Absolute path traversal vulnerability in recordings/misc/audio.php in the Asterisk Recording Interface (ARI) web interface in Asterisk@Home before 2.8 allows remote attackers to read arbitrary MP3, WAV, and GSM files via a full pathname in the recording parameter.  NOTE: this issue can also be used to determine existence of files.

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

It affects 1 product.


Products: Asteriskathome Asteriskathome.

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

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

## Is CVE-2006-2021 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2020](https://insights.sbomify.com/CVE-2006-2020/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2021 is a medium-severity path traversal vulnerability in n/a, published on 25 Apr 2006. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2021 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-2021/ (Markdown: https://insights.sbomify.com/CVE-2006-2021/index.md)
```

## Sources

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

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