# CVE-2007-1595: Code injection in n/a

> Remote attackers can execute arbitrary extensions in Asterisk PBX by specifying invalid extensions, potentially leading to code execution.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 22 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1595, GHSA-2h5w-3h6g-pgqq

## What is CVE-2007-1595?

CVE-2007-1595 is a high-severity code injection vulnerability in n/a, published on 22 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Asterisk Extension Language (AEL) in pbx/pbx_ael.c in Asterisk does not properly generate extensions, which allows remote attackers to execute arbitrary extensions and have an unknown impact by specifying an invalid extension in a certain form.

## Which versions are affected by CVE-2007-1595?

It affects 1 product.


Products: Asterisk Asterisk.

## How do I fix CVE-2007-1595?

Upgrade to a fixed version.

## Is CVE-2007-1595 being exploited?

There is no known exploitation of CVE-2007-1595 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-2488](https://insights.sbomify.com/CVE-2007-2488/): Null dereference in n/a (critical 10.0)
- [CVE-2008-1390](https://insights.sbomify.com/CVE-2008-1390/): Weak cryptography in n/a (critical 9.3)
- [CVE-2007-3762](https://insights.sbomify.com/CVE-2007-3762/): Memory corruption in n/a (critical 9.3)
- [CVE-2008-1332](https://insights.sbomify.com/CVE-2008-1332/): Auth bypass in n/a (high 8.8)
- [CVE-2008-3263](https://insights.sbomify.com/CVE-2008-3263/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1595 and fix it if it is affected.

What it is: CVE-2007-1595 is a high-severity code injection vulnerability in n/a, published on 22 Mar 2007. 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-2007-1595 in the wild and no public exploit code.

Affected product: n/a. 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-2007-1595/ (Markdown: https://insights.sbomify.com/CVE-2007-1595/index.md)
```

## Sources

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

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