Loading vulnerability…
KeePass Password Safe through 2.53, in a default installation, allows an attacker who can write to the KeePass XML configuration file to inject malicious event-condition-action triggers (TriggerSystem). By adding an export trigger, the attacker can cause KeePass to export the password database contents and thereby obtain stored credentials in cleartext. The vendor notes that an attacker with write access to the configuration file effectively already has a high level of local access, and therefore no patch is provided.
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 provides a proof-of-concept (POC) exploit and a configuration scanner for CVE-2023-24055, a vulnerability in KeePass on Windows. The main exploit (poc.py) is a Python script that modifies the KeePass configuration file (%APPDATA%\KeePass\KeePass.config.xml) to add a malicious trigger. This trigger causes KeePass to export the current database to a plaintext CSV file (c:\Users\%USERNAME%\KeepassExport.csv) without requiring the master password, by setting the ExportNoKey policy to true. The script does not perform any safety checks or backups, and may corrupt the configuration file if misused. The config_scanner.py script is a utility to parse and display triggers and certain policies from the KeePass configuration file, highlighting potentially dangerous actions. The repository is structured with two main Python scripts (poc.py and config_scanner.py), a README with detailed explanations, and standard license and gitignore files. The exploit requires local access to the target system and sufficient permissions to modify the KeePass configuration 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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.