# CVE-2001-1333: Path traversal in n/a

> Local attackers can exploit insecure temporary file handling in CUPS to overwrite arbitrary files via symlink attacks.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/A:N`)
- **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:** No
- **Published:** 3 May 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gvch-hcwr-7gw3

## What is CVE-2001-1333?

CVE-2001-1333 is a low-severity path traversal vulnerability in n/a, published on 3 May 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Linux CUPS before 1.1.6 does not securely handle temporary files, possibly due to a symlink vulnerability that could allow local users to overwrite files.

## Which versions are affected by CVE-2001-1333?

It affects 1 product.


Products: Easy Software Products Cups.

## How do I fix CVE-2001-1333?

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

## Is CVE-2001-1333 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0194](https://insights.sbomify.com/CVE-2001-0194/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5849](https://insights.sbomify.com/CVE-2007-5849/): Integer overflow in n/a (critical 9.3)
- [CVE-2004-1125](https://insights.sbomify.com/CVE-2004-1125/): Memory corruption in n/a (critical 9.3)
- [CVE-2002-0063](https://insights.sbomify.com/CVE-2002-0063/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1332](https://insights.sbomify.com/CVE-2001-1332/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1333 and fix it if it is affected.

What it is: CVE-2001-1333 is a low-severity path traversal vulnerability in n/a, published on 3 May 2002. 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-2001-1333 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-2001-1333/ (Markdown: https://insights.sbomify.com/CVE-2001-1333/index.md)
```

## Sources

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

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