# CVE-2007-5849: Integer overflow in n/a

> Remote attackers can execute arbitrary code on CUPS servers via crafted SNMP responses due to an integer underflow leading to buffer overflow.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Dec 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5849, GHSA-x2h6-2q5c-v7px

## What is CVE-2007-5849?

CVE-2007-5849 is a critical vulnerability in n/a, published on 19 Dec 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer underflow in the asn1_get_string function in the SNMP back end (backend/snmp.c) for CUPS 1.2 through 1.3.4 allows remote attackers to execute arbitrary code via a crafted SNMP response that triggers a stack-based buffer overflow.

Weakness: CWE-189

## Which versions are affected by CVE-2007-5849?

It affects 1 product.


Products: Easy Software Products Cups.

## How do I fix CVE-2007-5849?

Upgrade to a fixed version.

## Is CVE-2007-5849 being exploited?

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

Public exploit code:

- Common UNIX Printing System 1.2/1.3 SNMP - 'asn1_get_string()' Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0194](https://insights.sbomify.com/CVE-2001-0194/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1125](https://insights.sbomify.com/CVE-2004-1125/): Memory corruption in n/a (critical 9.3)
- [CVE-2002-0063](https://insights.sbomify.com/CVE-2002-0063/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1332](https://insights.sbomify.com/CVE-2001-1332/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1384](https://insights.sbomify.com/CVE-2002-1384/): Integer overflow in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5849 and fix it if it is affected.

What it is: CVE-2007-5849 is a critical vulnerability in n/a, published on 19 Dec 2007. 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-2007-5849 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-2007-5849/ (Markdown: https://insights.sbomify.com/CVE-2007-5849/index.md)
```

## Sources

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

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