# CVE-2009-0490: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause a crash in Audacity by tricking users into opening a malicious .gro file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0490, DTSA-192-1, GHSA-8f8x-6454-8222

## What is CVE-2009-0490?

CVE-2009-0490 is a critical memory corruption vulnerability in n/a, published on 10 Feb 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in the String_parse::get_nonspace_quoted function in lib-src/allegro/strparse.cpp in Audacity 1.2.6 and other versions before 1.3.6 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a .gro file containing a long string.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2009-0490?

It affects 1 product.


Products: Audacityteam Audacity.

## How do I fix CVE-2009-0490?

Upgrade to a fixed version.

## Is CVE-2009-0490 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0490 exists.

Public exploit code:

- Audacity 1.2.6 - '.gro' Local Buffer Overflow (PoC) (exploitdb)
- Audacity 1.2 - '.gro' Universal Buffer Overflow (Egghunter) (exploitdb)
- Audacity 1.2.6 - '.gro' Local Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [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-2007-6061](https://insights.sbomify.com/CVE-2007-6061/): Path traversal in n/a (medium 5.0)
- [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-2009-0490 and fix it if it is affected.

What it is: CVE-2009-0490 is a critical memory corruption vulnerability in n/a, published on 10 Feb 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0490 exists.

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-2009-0490/ (Markdown: https://insights.sbomify.com/CVE-2009-0490/index.md)
```

## Sources

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

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