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

> User-assisted attackers can cause a crash or hang in the screen terminal emulator by sending specific UTF-8 sequences.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-4573, DSA-1202-1, GHSA-5v6p-jx73-rq6x

## What is CVE-2006-4573?

CVE-2006-4573 is a low-severity denial of service vulnerability in n/a, published on 24 Oct 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Multiple unspecified vulnerabilities in the "utf8 combining characters handling" (utf8_handle_comb function in encoding.c) in screen before 4.0.3 allows user-assisted attackers to cause a denial of service (crash or hang) via certain UTF8 sequences.

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

It affects 1 product.


Products: Gnu Screen.

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

Upgrade to a fixed version.

## Is CVE-2006-4573 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0972](https://insights.sbomify.com/CVE-2003-0972/): Integer overflow in n/a (critical 10.0)
- [CVE-2020-9366](https://insights.sbomify.com/CVE-2020-9366/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-5618](https://insights.sbomify.com/CVE-2017-5618/): Privilege escalation in n/a (high 7.8)
- [CVE-2007-3048](https://insights.sbomify.com/CVE-2007-3048/): Auth bypass in n/a (high 7.2)
- [CVE-2023-24626](https://insights.sbomify.com/CVE-2023-24626/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4573 is a low-severity denial of service vulnerability in n/a, published on 24 Oct 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-4573 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-4573/ (Markdown: https://insights.sbomify.com/CVE-2006-4573/index.md)
```

## Sources

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

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