# CVE-2015-3008: Security feature bypass in n/a

> Man-in-the-middle attackers can spoof SSL servers via crafted certificates due to improper null byte handling in SIP TLS registration.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-3008, GHSA-j3c8-xv8h-h8mv, MGASA-2015-0153, UBUNTU-CVE-2015-3008

## What is CVE-2015-3008?

CVE-2015-3008 is a medium-severity vulnerability in Digium Asterisk, published on 10 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Asterisk Open Source 1.8 before 1.8.32.3, 11.x before 11.17.1, 12.x before 12.8.2, and 13.x before 13.3.2 and Certified Asterisk 1.8.28 before 1.8.28-cert5, 11.6 before 11.6-cert11, and 13.1 before 13.1-cert2, when registering a SIP TLS device, does not properly handle a null byte in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority.

Weakness: CWE-310

## Which versions are affected by CVE-2015-3008?

It affects 2 products.


Products: Digium Asterisk, Digium Certified Asterisk.

## How do I fix CVE-2015-3008?

Upgrade to a fixed version.

## Is CVE-2015-3008 being exploited?

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

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

## Sources

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

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