# CVE-2019-7733: Integer overflow in n/a

> An attacker can trigger a buffer overflow via a large Content-Length header, potentially leading to code execution or denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-7733, GHSA-h9ch-cxcp-w4q8, UBUNTU-CVE-2019-7733

## What is CVE-2019-7733?

CVE-2019-7733 is a high-severity vulnerability in n/a, published on 11 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Live555 0.95, there is a buffer overflow via a large integer in a Content-Length HTTP header because handleRequestBytes has an unrestricted memmove.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2019-7733?

It affects 1 product.


Products: Live555 Streaming Media.

## How do I fix CVE-2019-7733?

Upgrade to a fixed version.

## Is CVE-2019-7733 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15232](https://insights.sbomify.com/CVE-2019-15232/): Use after free in n/a (critical 9.8)
- [CVE-2021-28899](https://insights.sbomify.com/CVE-2021-28899/): Denial of service in n/a (high 7.5)
- [CVE-2019-7732](https://insights.sbomify.com/CVE-2019-7732/): Denial of service in n/a (high 7.5)
- [CVE-2013-6933](https://insights.sbomify.com/CVE-2013-6933/): Integer overflow in n/a (high 7.5)
- [CVE-2013-6934](https://insights.sbomify.com/CVE-2013-6934/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7733 and fix it if it is affected.

What it is: CVE-2019-7733 is a high-severity vulnerability in n/a, published on 11 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7733 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-2019-7733/ (Markdown: https://insights.sbomify.com/CVE-2019-7733/index.md)
```

## Sources

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

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