# CVE-2006-7220: Denial of service in n/a

> Remote attackers can crash SAP print services via malicious print job requests, causing denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jchx-wq68-4727

## What is CVE-2006-7220?

CVE-2006-7220 is a high-severity denial of service vulnerability in n/a, published on 10 Jul 2007. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in SAP SAPLPD and SAPSPRINT allows remote attackers to cause a denial of service (application crash) via a certain print job request.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2006-7220?

It affects 2 products.


Products: Sap Saplpd, Sap Sapsprint.

## How do I fix CVE-2006-7220?

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

## Is CVE-2006-7220 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10079](https://insights.sbomify.com/CVE-2016-10079/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7220 and fix it if it is affected.

What it is: CVE-2006-7220 is a high-severity denial of service vulnerability in n/a, published on 10 Jul 2007. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-7220 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-2006-7220/ (Markdown: https://insights.sbomify.com/CVE-2006-7220/index.md)
```

## Sources

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

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