Loading vulnerability…
Asterisk versions before 18.24.2, 20.9.2, and 21.4.2, and Certified Asterisk versions before 18.9-cert11 and 20.7-cert2, allow an authenticated Asterisk Manager Interface (AMI) user granted the originate write permission to modify Asterisk configuration files. The user can retrieve remote content and write it to disk, and can append content to existing configuration files through the FILE function used within the SET application. The resulting unauthorized configuration modification can enable privilege escalation, remote code execution, or blind server-side request forgery using arbitrary protocols.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit module targeting CVE-2024-42365, a remote code execution vulnerability in Asterisk's AMI (Asterisk Manager Interface). The exploit leverages an authenticated AMI user with 'write=originate' permissions to modify configuration files (notably /etc/asterisk/extensions.conf) and inject a malicious extension that executes arbitrary system commands as the Asterisk service user. The payload is base64-encoded and executed via bash, allowing for flexible command execution (e.g., reverse shell). The module requires valid AMI credentials and targets Asterisk versions prior to 18.24.2, 20.9.2, 21.4.2, and certified-asterisk 18.9-cert11/20.7-cert2. The attack vector is network-based, exploiting the AMI service. The repository is structured as a typical Metasploit exploit module written in Ruby, with all logic contained in a single file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.