# CVE-2014-8415: Race condition in n/a

> Remote attackers can crash Asterisk PBX via a race condition in the PJSIP channel driver, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8415, GHSA-g56f-mq6j-ppcx

## What is CVE-2014-8415?

CVE-2014-8415 is a medium-severity vulnerability in Digium Asterisk, published on 24 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Race condition in the chan_pjsip channel driver in Asterisk Open Source 12.x before 12.7.1 and 13.x before 13.0.1 allows remote attackers to cause a denial of service (assertion failure and crash) via a cancel request for a SIP session with a queued action to (1) answer a session or (2) send ringing.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-8415?

It affects 1 product.


Products: Digium Asterisk.

## How do I fix CVE-2014-8415?

Upgrade to a fixed version.

## Is CVE-2014-8415 being exploited?

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

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

## Sources

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

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