← Back to results
Vulnerability record · public intelligence
CVE-2024-42365
HIGH

Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan

Published Aug 8, 2024 · Updated Nov 3, 2026

Severity · CVSSHIGH · Not scored
Known exploitationNot listed
EPSS / likelihood4.70%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
IMMEDIATE
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Patch commit ↗
  4. Patch commit ↗
  5. Patch commit ↗
  6. Patch commit ↗
  7. Source repository ↗
  8. Source repository ↗
  9. lists.debian.org ↗

Record history

Published Aug 8, 2024 · Last refreshed Nov 3, 2026