CVE-2024-42365 json
Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan
published 2024-08-08 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-39574
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Metasploit
Summary
Asterisk is an open source private branch exchange (PBX) and telephony toolkit. Prior to asterisk versions 18.24.2, 20.9.2, and 21.4.2 and certified-asterisk versions 18.9-cert11 and 20.7-cert2, an AMI user with `write=originate` may change all configuration files in the `/etc/asterisk/` directory. This occurs because they are able to curl remote files and write them to disk, but are also able to append to existing files using the `FILE` function inside the `SET` application. This issue may result in privilege escalation, remote code execution and/or blind server-side request forgery with arbitrary protocol. Asterisk versions 18.24.2, 20.9.2, and 21.4.2 and certified-asterisk versions 18.9-cert11 and 20.7-cert2 contain a fix for this issue.
Patch / fix
- asterisk asterisk 18.24.2, 20.9.2, 21.4.2
- asterisk certified_asterisk 18.9-cert11, 20.7-cert2
- asterisk Debian 14 1:20.9.3~dfsg+~cs6.14.60671435-1
debian advisories DEBIAN-CVE-2024-42365
- asterisk Alpine 3.18, Alpine 3.17 18.24.3-r0
- asterisk Alpine 3.19 20.9.3-r0
- asterisk Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 20.9.2-r0
alpine advisories ALPINE-CVE-2024-42365
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-42365 updated cvss 8.8
asterisk: Write=originate, is sufficient permissions for code execution / System dialplan
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- First public exploit (Metasploit exploit/linux/misc/asterisk_ami_originate_auth_rce)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
4.70% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/linux/misc/asterisk_ami_originate_auth_rce Asterisk AMI Originate Authenticated RCE metasploit exploit, great rank, 2024-08-08
- github.com https://github.com/asterisk/asterisk/security/advisories/GHSA-c4cg-9275-6w44 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- asterisk asterisk
- asterisk certified_asterisk
Classification
References
-
github.com
/asterisk/asterisk/commit/42a2f4ccfa2c7062a15063e765916b3332e34cc4
patch
-
github.com
/asterisk/asterisk/commit/7a0090325bfa9d778a39ae5f7d0a98109e4651c8
patch
-
github.com
/asterisk/asterisk/commit/b4063bf756272254b160b6d1bd6e9a3f8e16cc71
patch
-
github.com
/asterisk/asterisk/commit/bbe68db10ab8a80c29db383e4dfe14f6eafaf993
patch
-
github.com
/asterisk/asterisk/commit/faddd99f2b9408b524e5eb8a01589fe1fa282df2
patch
-
github.com
/asterisk/asterisk/security/advisories/GHSA-c4cg-9275-6w44
exploit, technical-description, vendor-advisory
-
github.com
/asterisk/asterisk/blob/14367caaf7241df1eceea7c45c5b261989c2c6db/main/manager.c#L6426
issue-tracking
-
github.com
/asterisk/asterisk/blob/7d28165cb1b2d02d66e8693bd3fe23ee72fc55d8/main/manager.c#L6426
issue-tracking
- lists.debian.org /debian-lts-announce/2024/10/msg00016.html
Sources
- CVE List CVE-2024-42365
- NVD CVE-2024-42365
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.