# CVE-2017-16672: Denial of service in n/a

> A memory leak in Asterisk pjsip session handling allows attackers to exhaust memory and crash the service by rejecting calls.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** 9 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-16672, GHSA-6j42-f94q-5pq7, UBUNTU-CVE-2017-16672

## What is CVE-2017-16672?

CVE-2017-16672 is a medium-severity denial of service vulnerability in Digium Asterisk, published on 9 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Asterisk Open Source 13 before 13.18.1, 14 before 14.7.1, and 15 before 15.1.1 and Certified Asterisk 13.13 before 13.13-cert7. A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. Eventually Asterisk can run out of memory and crash.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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

It affects 2 products.


Products: Digium Asterisk, Digium Certified Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2017-16672 being exploited?

There is no known exploitation of CVE-2017-16672 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-2017-16672 and fix it if it is affected.

What it is: CVE-2017-16672 is a medium-severity denial of service vulnerability in Digium Asterisk, published on 9 Nov 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-16672 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-2017-16672/ (Markdown: https://insights.sbomify.com/CVE-2017-16672/index.md)
```

## Sources

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

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