CVE-2022-1257 is an insecure storage of sensitive information vulnerability affecting MA for Linux, macOS, and Windows prior to version 5.7.6. Sensitive information was stored in the ma.db database file without adequate protection, allowing a local user to access that data directly from local storage. The vendor indicates that the issue was addressed by moving the sensitive information into encrypted database files in version 5.7.6.
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 PowerShell proof-of-concept exploit for CVE-2022-1257, a vulnerability in McAfee (Trellix) Agent prior to version 5.7.6. The exploit targets the agent's database file (ma.db), which insecurely stores sensitive credentials. The script (CVE-2022-1257.ps1) copies the ma.db file to a temporary location, queries it for usernames and encrypted passwords, and then decrypts the passwords using a static XOR mask and 3DES with a hardcoded key. The output is a CSV of usernames and their decrypted passwords. The exploit requires local access to the target system, PowerShell 5.1+, and winsqlite3.dll (native to Windows 11). The repository also includes a README.md with detailed usage instructions, prerequisites, and references. No network endpoints are involved; the attack is purely local and file-based.
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.
4 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.