# CVE-2008-5744: Integer overflow in n/a

> Local users in the dialout group can overwrite kernel memory via an array index error in the Zaptel/DAHDI tor2 driver, potentially leading to privilege escalation.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-86mj-x9g2-c7rh

## What is CVE-2008-5744?

CVE-2008-5744 is a high-severity vulnerability in n/a, published on 26 Dec 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Array index error in the dahdi/tor2.c driver in Zaptel (aka DAHDI) 1.4.11 and earlier allows local users in the dialout group to overwrite an integer value in kernel memory by writing to /dev/zap/ctl, related to an incorrect tor2 patch for CVE-2008-5396 that uses the wrong variable in a range check against the value of lc->sync.

Weakness: CWE-189

## Which versions are affected by CVE-2008-5744?

It affects 1 product.


Products: Asterisk Zaptel.

## How do I fix CVE-2008-5744?

Apply the vendor's patch.

## Is CVE-2008-5744 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5396](https://insights.sbomify.com/CVE-2008-5396/): Integer overflow in n/a (high 7.2)
- [CVE-2007-5690](https://insights.sbomify.com/CVE-2007-5690/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5744 and fix it if it is affected.

What it is: CVE-2008-5744 is a high-severity vulnerability in n/a, published on 26 Dec 2008. 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-2008-5744 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-2008-5744/ (Markdown: https://insights.sbomify.com/CVE-2008-5744/index.md)
```

## Sources

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

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