# CVE-2018-7285: Null dereference in n/a

> A NULL pointer dereference in Asterisk's RTP handling allows remote attackers to cause a denial of service via crafted RTP packets.

- **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:** No
- **Published:** 22 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2pjx-4j7g-wf3f

## What is CVE-2018-7285?

CVE-2018-7285 is a high-severity vulnerability in Digium Asterisk, published on 22 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and desired payload numbers. While an SDP negotiation may result in a codec using a different payload number, these desired ones are still stored internally. When an RTP packet was received, this registry would be consulted if the payload number was not found in the negotiated SDP. This registry was incorrectly consulted for all packets, even those which are dynamic. If the payload number resulted in a codec of a different type than the RTP stream (for example, the payload number resulted in a video codec but the stream carried audio), a crash could occur if no stream of that type had been negotiated. This was due to the code incorrectly assuming that a stream of that type would always exist.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2018-7285?

It affects 1 product.


Products: Digium Asterisk.

## How do I fix CVE-2018-7285?

No fix has been published for CVE-2018-7285 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7285 being exploited?

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

What it is: CVE-2018-7285 is a high-severity vulnerability in Digium Asterisk, published on 22 Feb 2018. 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-2018-7285 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-2018-7285/ (Markdown: https://insights.sbomify.com/CVE-2018-7285/index.md)
```

## Sources

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

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