The STUN implementation in Asterisk 1.4.x before 1.4.8, AsteriskNOW before beta7, Appliance Developer Kit before 0.5.0, and s800i before 1.0
The STUN implementation in Asterisk 1.4.x before 1.4.8, AsteriskNOW before beta7, Appliance Developer Kit before 0.5.0, and s800i before 1.0.2 allows remote attackers to cause a denial of service (crash) via a crafted STUN length attribute in a STUN packet sent on an RTP port.
- Published
- Jul 18, 2007
- Updated
- Jun 16, 2026
- EPSS
- 1.7% · 76th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.7%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| asterisk | asterisk | cpe:2.3:a:asterisk:asterisk |
| asterisk | asterisk appliance developer kit | cpe:2.3:a:asterisk:asterisk_appliance_developer_kit |
| asterisk | asterisknow | cpe:2.3:a:asterisk:asterisknow |
| asterisk | s800i appliance | cpe:2.3:h:asterisk:s800i_appliance |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- asterisk asterisk1.0
- asterisk asterisk1.0.10
- asterisk asterisk1.0.11
- asterisk asterisk1.0.12
- asterisk asterisk1.0.6
- asterisk asterisk1.0.7
- asterisk asterisk1.0.8
- asterisk asterisk1.0.9
- asterisk asterisk1.2.0_beta1
- asterisk asterisk1.2.0_beta2
- asterisk asterisk1.2.10
- asterisk asterisk1.2.11
- asterisk asterisk1.2.12
- asterisk asterisk1.2.13
- asterisk asterisk1.2.14
- asterisk asterisk1.2.15
- asterisk asterisk1.2.16
- asterisk asterisk1.2.17
- asterisk asterisk1.2.5
- asterisk asterisk1.2.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | asterisk | before 1:1.4.8~dfsg-1 | 1:1.4.8~dfsg-1 |
Same product
asterisk: all recordsOther highest-scoring records for the same primary product.
- CVE-2007-2488The IAX2 channel driver (chan_iax2) in Asterisk before 20070504 does not properly null terminate data, which allows remote attackers to trig41Plan
- CVE-2008-3263The IAX2 protocol implementation in Asterisk Open Source 1.0.x, 1.2.x before 1.2.30, and 1.4.x before 1.4.21.2; Business Edition A.x.x, B.x.39Monitor
- CVE-2007-3762Stack-based buffer overflow in the IAX2 channel driver (chan_iax2) in Asterisk before 1.2.22 and 1.4.x before 1.4.8, Business Edition before39Monitor
- CVE-2008-1390The AsteriskGUI HTTP server in Asterisk Open Source 1.4.x before 1.4.19-rc3 and 1.6.x before 1.6.0-beta6, Business Edition C.x.x before C.1.38Monitor
- CVE-2007-2293Multiple stack-based buffer overflows in the process_sdp function in chan_sip.c of the SIP channel T.38 SDP parser in Asterisk before 1.4.3 37Monitor
- CVE-2024-42365Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:asterisk | 1:1.4.8~dfsg-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- ftp.digium.com/pub/asa/ASA-2007-017.pdf
- secunia.com/advisories/26099
- www.securityfocus.com/bid/24950
- www.securitytracker.com/id?1018407
- www.vupen.com/english/advisories/2007/2563
- exchange.xforce.ibmcloud.com/vulnerabilities/35480
Vendor advisories and official records. Exploit/PoC links are deliberately left out.