# CVE-2017-9372: Memory corruption in n/a

> Remote attackers can crash Asterisk PBX via crafted SIP packets, causing 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:** 2 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f9w9-cxp5-6pq8, UBUNTU-CVE-2017-9372

## What is CVE-2017-9372?

CVE-2017-9372 is a high-severity memory corruption vulnerability in Digium Certified Asterisk, published on 2 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PJSIP, as used in Asterisk Open Source 13.x before 13.15.1 and 14.x before 14.4.1, Certified Asterisk 13.13 before 13.13-cert4, and other products, allows remote attackers to cause a denial of service (buffer overflow and application crash) via a SIP packet with a crafted CSeq header in conjunction with a Via header that lacks a branch parameter.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-9372?

It affects 2 products.


Products: Digium Certified Asterisk, Digium Open Source.

## How do I fix CVE-2017-9372?

Upgrade to a fixed version.

## Is CVE-2017-9372 being exploited?

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

## Other vulnerabilities in Digium Certified Asterisk

- [CVE-2017-9359](https://insights.sbomify.com/CVE-2017-9359/): Denial of service in n/a (high 7.5)
- [CVE-2020-28327](https://insights.sbomify.com/CVE-2020-28327/): Race condition in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9372 and fix it if it is affected.

What it is: CVE-2017-9372 is a high-severity memory corruption vulnerability in Digium Certified Asterisk, published on 2 Jun 2017. 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-2017-9372 in the wild and no public exploit code.

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

## Sources

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

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