Loading vulnerability…
MySQL 3.23.55 and earlier creates world-writeable files. A MySQL user can use the SELECT ... INTO OUTFILE operation to overwrite a MySQL configuration file, such as my.cnf. On a subsequent restart, the modified configuration can cause MySQL to run as root, resulting in local privilege escalation.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
Historical MySQL configuration-file creation vulnerability fixed in MySQL version 3.23.55; referenced for background and comparison with CVE-2016-6662.
A historical MySQL configuration-file creation vulnerability fixed in MySQL 3.23.55. It is cited as background for the configuration-file injection protections bypassed by CVE-2016-6662.
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.