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

> Remote authenticated users can crash Asterisk via a crafted SDP message due to an integer signedness error in the RTP module.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2019-7251, DEBIAN-CVE-2019-7251, GHSA-686h-j227-6632, UBUNTU-CVE-2019-7251

## What is CVE-2019-7251?

CVE-2019-7251 is a medium-severity vulnerability in Digium Asterisk, published on 28 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Integer Signedness issue (for a return code) in the res_pjsip_sdp_rtp module in Digium Asterisk versions 15.7.1 and earlier and 16.1.1 and earlier allows remote authenticated users to crash Asterisk via a specially crafted SDP protocol violation.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Digium Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2019-7251 being exploited?

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

## Other vulnerabilities in Digium Asterisk

- [CVE-2017-14100](https://insights.sbomify.com/CVE-2017-14100/): Command injection in n/a (critical 9.8)
- [CVE-2014-8418](https://insights.sbomify.com/CVE-2014-8418/): Privilege escalation in n/a (critical 9.0)
- [CVE-2011-1599](https://insights.sbomify.com/CVE-2011-1599/): Missing authorization in n/a (critical 9.0)
- [CVE-2017-16671](https://insights.sbomify.com/CVE-2017-16671/): Memory corruption in n/a (high 8.8)
- [CVE-2017-7617](https://insights.sbomify.com/CVE-2017-7617/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-7251 is a medium-severity vulnerability in Digium Asterisk, published on 28 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7251 in the wild and no public exploit code.

Affected product: Digium Asterisk. 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-7251/ (Markdown: https://insights.sbomify.com/CVE-2019-7251/index.md)
```

## Sources

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

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