Loading vulnerability…
CVE-2023-3722 is an OS command injection vulnerability in the Avaya Aura Device Services Web application. According to the provided content, the flaw can be triggered through a malicious uploaded file, leading to remote code execution in the context of the Web server user. The issue affects Avaya Aura Device Services version 8.1.4.0 and earlier. Specific vulnerable functions or code paths are not provided in the available information.
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.
This repository contains a Python proof-of-concept exploit for CVE-2023-3722, a remote code execution vulnerability in Avaya Aura Device Services due to unrestricted file upload. The main file, CVE-2023-3722.py, uploads a PHP webshell to the target server using an HTTP PUT request to the /PhoneBackup/ directory, with a randomly generated filename. It then executes arbitrary system commands by sending a GET request to the uploaded PHP file, returning the command output. The exploit requires the attacker to specify the target hostname (and port) and optionally a command to execute (default is 'id'). The README.md provides usage instructions. The exploit demonstrates operational maturity, as it provides a working payload and automates the attack process. The main attack vector is network-based, targeting the HTTPS service of the vulnerable Avaya product.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.