# CVE-2014-6610: Denial of service in n/a

> Remote authenticated users can crash Asterisk via malformed fax messages when the spandsp module is enabled.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **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:** 26 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-6610, GHSA-f9gh-gm49-v657, MGASA-2014-0490

## What is CVE-2014-6610?

CVE-2014-6610 is a medium-severity denial of service vulnerability in Digium Asterisk, published on 26 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dialplan application.

Weakness: CWE-19

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

It affects 2 products.


Products: Digium Asterisk, Digium Certified Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2014-6610 being exploited?

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

What it is: CVE-2014-6610 is a medium-severity denial of service vulnerability in Digium Asterisk, published on 26 Nov 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-6610 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-6610/ (Markdown: https://insights.sbomify.com/CVE-2014-6610/index.md)
```

## Sources

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

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