CVE-2014-125125 is a path traversal vulnerability in A10 Networks AX Loadbalancer versions 2.6.1-GR1-P5, 2.7.0, and earlier. The flaw is in the /xml/downloads endpoint’s handling of the filename parameter, which does not properly sanitize user-supplied input. By supplying crafted directory traversal sequences in an HTTP request, an unauthenticated remote attacker can cause the appliance to access files outside the intended directory and return their contents. The vulnerable endpoint also deletes the retrieved file from the system after download, making the issue both an arbitrary file read and unintended file deletion condition. Sensitive material such as SSL certificates and private keys may be exposed.
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 single Metasploit auxiliary scanner module targeting a directory traversal vulnerability in A10 Networks AX Loadbalancer (hardware and VM) versions 2.6.1-GR1-P5, 2.7.0, and below. The exploit abuses improper validation of the 'filename' parameter in the /xml/downloads endpoint, allowing an attacker to read arbitrary files from the device by sending a crafted HTTP GET request. Notably, the exploit will also delete the file after downloading it, requiring explicit user confirmation via the CONFIRM_DELETE option. The module is written in Ruby and leverages Metasploit's HTTP client and scanner mixins. The main entry point is the 'run_host' method, which constructs the traversal payload and handles the response. The exploit is operational and can be used to extract sensitive files such as SSL certificates from vulnerable devices.
3 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.