CVE-2024-29851 is a vulnerability in Veeam Backup Enterprise Manager that allows a high-privileged or privileged user to obtain the NTLM hash of the Enterprise Manager service account. The issue is exposed when the Enterprise Manager service is configured to run under a service account other than the default Local System account. Successful exploitation enables theft of the service account’s NTLM credential material, which can then be used in follow-on authentication attacks. The available information identifies the flaw as affecting Veeam Backup Enterprise Manager and being remediated in version 12.1.2.172.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Vulnerability allowing a privileged user to steal the NTLM hash of the Veeam Backup Enterprise Manager service account when it is not running as the default Local System account.
A vulnerability in Veeam Backup Enterprise Manager that can allow a privileged user to steal NTLM hashes of the product's service account under certain service-account configuration conditions.
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.