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

> Remote attackers can read arbitrary files via directory traversal in the TFTP service of Fujitsu SystemcastWizard Lite.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hx3q-q8j3-vfhr

## What is CVE-2009-0271?

CVE-2009-0271 is a medium-severity path traversal vulnerability in n/a, published on 26 Jan 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the TFTP service in Fujitsu SystemcastWizard Lite 2.0A, 2.0, 1.9, and earlier allows remote attackers to read arbitrary files via directory traversal sequences in unspecified vectors.

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

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

It affects 1 product.


Products: Fujitsu Systemcastwizard Lite.

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

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

## Is CVE-2009-0271 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0264](https://insights.sbomify.com/CVE-2009-0264/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-0270](https://insights.sbomify.com/CVE-2009-0270/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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