# CVE-2009-0521: Path traversal in n/a

> Local attackers can exploit an untrusted search path in Adobe Flash Player on Linux to gain privileges or access sensitive information via a crafted library.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h35j-98vm-989g

## What is CVE-2009-0521?

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

### Official description

Untrusted search path vulnerability in Adobe Flash Player 9.x before 9.0.159.0 and 10.x before 10.0.22.87 on Linux allows local users to obtain sensitive information or gain privileges via a crafted library in a directory contained in the RPATH.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Adobe Flash Player for Linux.

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

Upgrade to a fixed version.

## Is CVE-2009-0521 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5499](https://insights.sbomify.com/CVE-2008-5499/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0521 and fix it if it is affected.

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

## Sources

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

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