# CVE-2002-1275: Code injection in n/a

> Remote attackers can execute arbitrary code via unsanitized input in the html2ps converter when used with LPRng.

- **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:** Yes
- **Published:** 10 Nov 2002
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-1275, DSA-192, GHSA-x9x9-cfm2-jg93

## What is CVE-2002-1275?

CVE-2002-1275 is a high-severity code injection vulnerability in n/a, published on 10 Nov 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unknown vulnerability in html2ps HTML/PostScript converter 1.0, when used within LPRng, allows remote attackers to execute arbitrary code via "unsanitized input."

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

It affects 1 product.


Products: Html2ps Project Html2ps.

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

Apply the vendor's patch.

## Is CVE-2002-1275 being exploited?

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

Public exploit code:

- LPRNG html2ps 1.0 - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-5067](https://insights.sbomify.com/CVE-2009-5067/): Path traversal in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1275 is a high-severity code injection vulnerability in n/a, published on 10 Nov 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1275 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-1275/ (Markdown: https://insights.sbomify.com/CVE-2002-1275/index.md)
```

## Sources

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

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