# CVE-2007-5690: Memory corruption in n/a

> Local attackers with root access could exploit a buffer overflow in the Zaptel driver to potentially escalate privileges, though the vendor disputes the security impact.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9phc-ffmq-gxh2

## What is CVE-2007-5690?

CVE-2007-5690 is a medium-severity memory corruption vulnerability in n/a, published on 29 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in sethdlc.c in the Asterisk Zaptel 1.4.5.1 might allow local users to gain privileges via a long device name (interface name) in the ifr_name field.  NOTE: the vendor disputes this issue, stating that the application requires root access, so privilege boundaries are not crossed

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

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

It affects 1 product.


Products: Asterisk Zaptel.

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

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

## Is CVE-2007-5690 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5744](https://insights.sbomify.com/CVE-2008-5744/): Integer overflow in n/a (high 7.2)
- [CVE-2008-5396](https://insights.sbomify.com/CVE-2008-5396/): Integer overflow in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5690 is a medium-severity memory corruption vulnerability in n/a, published on 29 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5690 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-5690/ (Markdown: https://insights.sbomify.com/CVE-2007-5690/index.md)
```

## Sources

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

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