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

> Remote attackers can cause denial of service in Monopd by sending strings with many escaped characters, leading to excessive CPU and memory consumption.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 7 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1046, GHSA-xm86-62fx-w5xf

## What is CVE-2006-1046?

CVE-2006-1046 is a medium-severity denial of service vulnerability in n/a, published on 7 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

server.cpp in Monopd 0.9.3 allows remote attackers to cause a denial of service (CPU and memory consumption) via a string containing a large number of characters that are escaped when Monopd produces XML output.

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

It affects 1 product.


Products: Monopd Monopd.

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

Upgrade to a fixed version.

## Is CVE-2006-1046 being exploited?

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

Public exploit code:

- Monopd 0.9.3 - Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1046 is a medium-severity denial of service vulnerability in n/a, published on 7 Mar 2006. 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-2006-1046 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-2006-1046/ (Markdown: https://insights.sbomify.com/CVE-2006-1046/index.md)
```

## Sources

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

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