CVE-2010-0685: The design of the dialplan functionality in Asterisk Open Source 1.2.x, 1.4.x, and 1.6.x; and Asterisk Business Edition B.x.x and C.x.x…
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 72.3% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: asterisk (Debian:14) 1:1.6.2.6-1.
Low priority for now. Upgrade to asterisk (Debian:14) 1:1.6.2.6-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The design of the dialplan functionality in Asterisk Open Source 1.2.x, 1.4.x, and 1.6.x; and Asterisk Business Edition B.x.x and C.x.x, when using the ${EXTEN} channel variable and wildcard pattern matches, allows context-dependent attackers to inject strings into the dialplan using metacharacters that are injected when the variable is expanded, as demonstrated using the Dial application to process a crafted SIP INVITE message that adds an unintended outgoing channel leg. NOTE: it could be argued that this is not a vulnerability in Asterisk, but a class of vulnerabilities that can occur in any program that uses this feature without the associated filtering functionality that is already available.
- Published
- Feb 23, 2010
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 72th percentile
- CWE
- —
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| digium | asterisk | cpe:2.3:a:digium:asterisk |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- digium asterisk1.2.0
- digium asterisk1.2.1
- digium asterisk1.2.10
- digium asterisk1.2.11
- digium asterisk1.2.12
- digium asterisk1.2.12.1
- digium asterisk1.2.13
- digium asterisk1.2.14
+12 more rows
- digium asterisk1.2.15
- digium asterisk1.2.16
- digium asterisk1.2.17
- digium asterisk1.2.18
- digium asterisk1.2.19
- digium asterisk1.2.2
- digium asterisk1.2.20
- digium asterisk1.2.21
- digium asterisk1.2.21.1
- digium asterisk1.2.22
- digium asterisk1.2.23
- digium asterisk1.2.24
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.6.2.6-1 | 1:1.6.2.6-1 |
Same product
digium: all recordsOther highest-scoring records for the same primary product.
- CVE-2006-5444Integer overflow in the get_input function in the Skinny channel driver (chan_skinny.c) in Asterisk 1.0.x before 1.0.12 and 1.2.x before…56Plan
- CVE-2017-17850An issue was discovered in Asterisk 13.18.4 and older, 14.7.4 and older, 15.1.4 and older, and 13.18-cert1 and older.53Plan
- CVE-2019-18610An issue was discovered in manager.c in Sangoma Asterisk through 13.x, 16.x, 17.x and Certified Asterisk 13.21 through 13.21-cert4.50Plan
Published before and after this one in the same product
- ← EarlierCVE-2009-3727Nov 10, 2009 · Asterisk Open Source 1.2.x before 1.2.35, 1.4.x before 1.4.26.3, 1.6.0.x before 1.6.0.17, and 1.6.1.x before 1.6.1.9; Business Edition…21Monitor
- ← EarlierCVE-2009-4055Dec 2, 2009 · rtp.c in Asterisk Open Source 1.2.x before 1.2.37, 1.4.x before 1.4.27.1, 1.6.0.x before 1.6.0.19, and 1.6.1.x before 1.6.1.11; Business…21Monitor
- Later →CVE-2010-1224Apr 1, 2010 · main/acl.c in Asterisk Open Source 1.6.0.x before 1.6.0.25, 1.6.1.x before 1.6.1.17, and 1.6.2.x before 1.6.2.5 does not properly enforce…18Monitor
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.6.2.6-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:N/I:P/A:N
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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- secunia.com/advisories/38641
- secunia.com/advisories/39096
- svn.asterisk.org/svn/asterisk/branches/1.2/README-SERIOUSLY.bestpractices.txt
- www.securityfocus.com/archive/1/509608/100/0/threaded
- www.securitytracker.com/id?1023637
- www.vupen.com/english/advisories/2010/0439
- exchange.xforce.ibmcloud.com/vulnerabilities/56397
Vendor advisories and official records. Exploit/PoC links are deliberately left out.