CVE-2008-5744

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2008-12-26 21:30 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:00 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 7.2 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2008-12-26 21:30 UTC

Last modified

2026-06-16 23:00 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-189

Record status

Modified

Affected

• Asterisk Zaptel ≤ 1.4.11
• Asterisk Zaptel 1.2
• Asterisk Zaptel 1.2.27
• Asterisk Zaptel 1.4

Attack profile CVSS 2.0 · 7.2

Attack vector

Local

Complexity

Low

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2008-5744.md and follow it. Check whether this project is affected by CVE-2008-5744. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge