# CVE-2002-0244: Path traversal in n/a

> Attackers can escape the chroot jail in AtheOS via directory traversal in the chdir function, potentially gaining unauthorized access to the filesystem.

- **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:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-24q4-rxhj-p299

## What is CVE-2002-0244?

CVE-2002-0244 is a high-severity path traversal vulnerability in n/a, published on 3 May 2002. 

### Official description

Directory traversal vulnerability in chroot function in AtheOS 0.3.7 allows attackers to escape the jail via a .. (dot dot) in the pathname argument to chdir.

## Which versions are affected by CVE-2002-0244?

It affects 1 product.


Products: Atheos Atheos.

## How do I fix CVE-2002-0244?

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

## Is CVE-2002-0244 being exploited?

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

Public exploit code:

- AtheOS 0.3.7 - Change Root Directory Escaping (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0244 and fix it if it is affected.

What it is: CVE-2002-0244 is a high-severity path traversal vulnerability in n/a, published on 3 May 2002. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0244 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-2002-0244/ (Markdown: https://insights.sbomify.com/CVE-2002-0244/index.md)
```

## Sources

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

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