Zaptel vulnerabilitiesRanked by how likely they are to be used.
Zaptel is made by Asterisk. We track 3 published vulnerabilities in it, across 4 versions. None of them is on the list of flaws known to be exploited today. If you run Zaptel, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Zaptel vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Zaptel's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Zaptel flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.5%CVE-2008-5744High
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...
- 0.4%CVE-2007-5690Medium
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.
- 0.3%CVE-2008-5396High
Array index error in the (1) torisa.c and (2) dahdi/tor2.c drivers 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...
Running Zaptel? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Zaptel on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Zaptel, across 4 versions.
None of Zaptel's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Zaptel. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.