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

> Remote attackers can list files in arbitrary directories via directory traversal in MyPic, exposing sensitive file structures.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h2gw-5pqv-cgrc

## What is CVE-2009-1737?

CVE-2009-1737 is a high-severity path traversal vulnerability in n/a, published on 20 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in bom.php in MyPic 2.1 allows remote attackers to list files in arbitrary directories via a .. (dot dot) in the dir parameter.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Diqiye Mypic.

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

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

## Is CVE-2009-1737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1737 is a high-severity path traversal vulnerability in n/a, published on 20 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-1737 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-1737/ (Markdown: https://insights.sbomify.com/CVE-2009-1737/index.md)
```

## Sources

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

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