# CVE-2017-7617: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Asterisk servers via a buffer overflow in the CDR user field handling.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 10 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-7617, GHSA-fw6v-c6vw-rqq9, UBUNTU-CVE-2017-7617

## What is CVE-2017-7617?

CVE-2017-7617 is a high-severity memory corruption vulnerability in Digium Asterisk, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Remote code execution can occur in Asterisk Open Source 13.x before 13.14.1 and 14.x before 14.3.1 and Certified Asterisk 13.13 before 13.13-cert3 because of a buffer overflow in a CDR user field, related to X-ClientCode in chan_sip, the CDR dialplan function, and the AMI Monitor action.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Digium Asterisk, Digium Certified Asterisk.

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

Upgrade to a fixed version.

## Is CVE-2017-7617 being exploited?

There is no known exploitation of CVE-2017-7617 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-2009-2726](https://insights.sbomify.com/CVE-2009-2726/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7617 and fix it if it is affected.

What it is: CVE-2017-7617 is a high-severity memory corruption vulnerability in Digium Asterisk, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7617 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-7617/ (Markdown: https://insights.sbomify.com/CVE-2017-7617/index.md)
```

## Sources

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

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