CVE-2024-42365: Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-42365?
CVE-2024-42365 has a critical severity rating due to the potential for an AMI user to modify system configuration files.
How do I fix CVE-2024-42365?
To fix CVE-2024-42365, upgrade to Asterisk versions 18.24.2, 20.9.2, 21.4.2, or the respective certified versions.
Which versions of Asterisk are affected by CVE-2024-42365?
Asterisk versions prior to 18.24.2, between 19.0.0 and 20.9.1, and 21.4.0 are affected by CVE-2024-42365.
What impact does CVE-2024-42365 have on Asterisk users?
CVE-2024-42365 allows unauthorized AMI users with 'write=originate' permissions to change configuration files, leading to potential system compromise.
Is there a workaround for CVE-2024-42365?
A temporary workaround for CVE-2024-42365 is to restrict AMI access and ensure proper authentication for users while upgrading is planned.