# CVE-2007-5488: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via source and destination numbers in Asterisk-Addons, potentially compromising call detail records.

- **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:** No
- **Published:** 17 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c3p6-f6m3-rwcg

## What is CVE-2007-5488?

CVE-2007-5488 is a high-severity SQL injection vulnerability in n/a, published on 17 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in cdr_addon_mysql in Asterisk-Addons before 1.2.8, and 1.4.x before 1.4.4, allow remote attackers to execute arbitrary SQL commands via the (1) source and (2) destination numbers, and probably (3) SIP URI, when inserting a record.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Asterisk Asterisk-Addons.

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

No fix has been published for CVE-2007-5488 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-5488 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5488 exists.

Public exploit code:

- Asterisk 'asterisk-addons' 1.2.7/1.4.3 - CDR_ADDON_MYSQL Module SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-2543](https://insights.sbomify.com/CVE-2008-2543/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5488 is a high-severity SQL injection vulnerability in n/a, published on 17 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5488 exists.

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-5488/ (Markdown: https://insights.sbomify.com/CVE-2007-5488/index.md)
```

## Sources

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

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