# CVE-2019-15297: Null dereference in n/a

> An attacker can crash the Asterisk PBX by sending a declined stream in a T.38 re-invite response, causing a null pointer dereference.

- **Severity:** Medium 6.5 (`CVSS:3.1/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:** 9 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2019-15297, DEBIAN-CVE-2019-15297, GHSA-qc2g-m5w4-ffmq, UBUNTU-CVE-2019-15297

## What is CVE-2019-15297?

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

### Official description

res_pjsip_t38 in Sangoma Asterisk 15.x before 15.7.4 and 16.x before 16.5.1 allows an attacker to trigger a crash by sending a declined stream in a response to a T.38 re-invite initiated by Asterisk. The crash occurs because of a NULL session media object dereference.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Digium Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2019-15297 being exploited?

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

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

## Sources

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

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