# CVE-2002-2218: Other in n/a

> CRLF injection in SIPS allows attackers to potentially gain privileges or modify configuration via crafted key values.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2006
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-62mq-8v6x-7m34

## What is CVE-2002-2218?

CVE-2002-2218 is a critical vulnerability in n/a, published on 13 Sep 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CRLF injection vulnerability in the setUserValue function in sipssys/code/site.inc.php in Haakon Nilsen simple, integrated publishing system (SIPS) before 20020209 has unknown impact, possibly gaining privileges or modifying critical configuration, via a CRLF sequence in a key value.

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

It affects 1 product.


Products: Sips Sips.

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

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

## Is CVE-2002-2218 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-1241](https://insights.sbomify.com/CVE-2000-1241/): Unspecified vulnerability in Haakon Nilsen simple, integrated publishing system (SIPS) before 0.2.4 has an unknown impact and attack vectors (critical 10.0)
- [CVE-2002-0267](https://insights.sbomify.com/CVE-2002-0267/): Privilege escalation in n/a (critical 10.0)
- [CVE-2006-4733](https://insights.sbomify.com/CVE-2006-4733/): File upload in n/a (high 7.5)
- [CVE-2003-1553](https://insights.sbomify.com/CVE-2003-1553/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2218 is a critical vulnerability in n/a, published on 13 Sep 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2218 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-2002-2218/ (Markdown: https://insights.sbomify.com/CVE-2002-2218/index.md)
```

## Sources

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

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