Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-42365: Asterisk allows `Write=originate` as sufficient permissions for code execution / `System()` dialplan

Noroxi assessment

Priority: Plan (action score 40/100)

  • A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
  • Because a ready-made attack tool exists, priority is at least “Plan”.
  • Probability of exploitation in the next 30 days: 4.7% (FIRST EPSS); higher than 91.8% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: asterisk (Alpine:v3.17) 18.24.3-r0; asterisk (Alpine:v3.19) 20.9.3-r0; asterisk (Alpine:v3.20) 20.9.2-r0.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to asterisk (Alpine:v3.17) 18.24.3-r0; asterisk (Alpine:v3.19) 20.9.3-r0; asterisk (Alpine:v3.20) 20.9.2-r0 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

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.

HighCVSS 8.8 · v3.1—Weaponized Fix available
Published
Aug 8, 2024
Updated
Jun 17, 2026
EPSS
4.7% · 91th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.7%
Ready-made attack tool
4 / 40 · floor: at least 40

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitHub_M
7.4
1.4 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-42365

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
asteriskasterisk
asteriskcertified asterisk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • asterisk asteriskbefore 18.24.2
  • asterisk asterisk19.0.0 and later · before 20.9.1
  • asterisk asterisk21.4.0
  • asterisk certified asterisk13.13.0
  • asterisk certified asterisk16.8
  • asterisk certified asterisk16.8.0
  • asterisk certified asterisk18.9
  • asterisk certified asterisk20.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • asterisk asterisk

    • < 18.24.2, >= 19.0.0, < 20.9.2, >= 21.0.0, < 21.4.2, < 18.9-cert11, >= 19.0, < 20.7-cert2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.17asteriskfrom 19.0.0 · before 18.24.3-r018.24.3-r0
Alpine:v3.19asteriskfrom 19.0.0 · before 20.9.3-r020.9.3-r0
Alpine:v3.20asteriskfrom 19.0.0 · before 20.9.2-r020.9.2-r0
Debian:11asteriskbefore 1:16.28.0~dfsg-0+deb11u51:16.28.0~dfsg-0+deb11u5
Debian:14asteriskbefore 1:20.9.3~dfsg+~cs6.14.60671435-11:20.9.3~dfsg+~cs6.14.60671435-1

Other 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 trig
    41Plan
  • 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 before
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2009-2346Sep 8, 2009 · The IAX2 protocol implementation in Asterisk Open Source 1.2.x before 1.2.35, 1.4.x before 1.4.26.2, 1.6.0.x before 1.6.0.15, and 1.6.1.x be
    32Monitor
  • ← EarlierCVE-2010-0441Feb 4, 2010 · Asterisk Open Source 1.6.0.x before 1.6.0.22, 1.6.1.x before 1.6.1.14, and 1.6.2.x before 1.6.2.2, and Business Edition C.3 before C.3.3.2,
    21Monitor
  • Later →CVE-2026-57184Oct 26, 2026 · Asterisk: Out-of-Bounds Read in Q.931 Information Element Parser (H.323 Addon)
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:asterisk18.24.3-r0 · Alpine:v3.17Package registry (OSV)
debian:asterisk1:20.9.3~dfsg+~cs6.14.60671435-1 · Debian:14Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Metasploit moduleexploit/linux/misc/asterisk_ami_originate_auth_rceAsterisk AMI Originate Authenticated RCEexploit2024-08-08
Proof-of-concept repository on GitHubstars:02026-08-30

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.

  1. Metasploit-1 d
  2. Published
  3. First PoC+751 d
  4. TodayNov 1, 2026+815 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records