# CVE-2005-1244: Path traversal in n/a

> Remote attackers can access arbitrary files via directory traversal in a NetIQ tool for iSeries AS/400 FTP servers, though the vendor disputes this vulnerability.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g47h-wpv4-rfwf

## What is CVE-2005-1244?

CVE-2005-1244 is a high-severity path traversal vulnerability in n/a, published on 24 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the third party tool from NetIQ, as used to secure the iSeries AS/400 FTP server, allows remote attackers to access arbitrary files, including those from qsys.lib, via ".." sequences in a GET request.  NOTE: the vendor has disputed this issue, saying that "neither NetIQ Security Manager nor our iSeries Security Solutions are vulnerable.

## Which versions are affected by CVE-2005-1244?

It affects 1 product.


Products: Netiq Pssecure.

## How do I fix CVE-2005-1244?

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

## Is CVE-2005-1244 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1244 and fix it if it is affected.

What it is: CVE-2005-1244 is a high-severity path traversal vulnerability in n/a, published on 24 Apr 2005. 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-2005-1244 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-2005-1244/ (Markdown: https://insights.sbomify.com/CVE-2005-1244/index.md)
```

## Sources

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

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