# CVE-2003-0972: Integer overflow in n/a

> Local attackers can execute arbitrary code via a buffer overflow caused by an integer signedness error in GNU screen escape sequence handling.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0972, DSA-408, GHSA-m666-c5wx-qfvx

## What is CVE-2003-0972?

CVE-2003-0972 is a critical vulnerability in n/a, published on 2 Dec 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer signedness error in ansi.c for GNU screen 4.0.1 and earlier, and 3.9.15 and earlier, allows local users to execute arbitrary code via a large number of ";" (semicolon) characters in escape sequences, which leads to a buffer overflow.

## Which versions are affected by CVE-2003-0972?

It affects 1 product.


Products: Gnu Screen.

## How do I fix CVE-2003-0972?

Upgrade to a fixed version.

## Is CVE-2003-0972 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2009-1214](https://insights.sbomify.com/CVE-2009-1214/): Information disclosure in n/a (medium 4.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0972 and fix it if it is affected.

What it is: CVE-2003-0972 is a critical vulnerability in n/a, published on 2 Dec 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0972 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-2003-0972/ (Markdown: https://insights.sbomify.com/CVE-2003-0972/index.md)
```

## Sources

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

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