Loading vulnerability…
A security feature bypass vulnerability in Windows Kerberos could allow an attacker to circumvent intended Kerberos security protections. The available information identifies the issue as affecting Windows Kerberos and classifies it as a security feature bypass, but does not provide technical detail about the vulnerable code path, protocol element, or specific implementation flaw.
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 Python exploit for CVE-2024-20674, a vulnerability in the client-side handling of Kerberos U2U TGT-REP in Microsoft Windows. The exploit enables a network Man-in-the-Middle (MITM) attacker to bypass Kerberos mutual authentication, allowing them to impersonate a Domain Controller (DC) and serve arbitrary Group Policy Objects (GPOs) to a victim Windows workstation. The main exploit logic is implemented in 'exploit.py', which sets up a Kerberos proxy and SMB server using Scapy, and manipulates Kerberos authentication flows to trigger the vulnerability. The 'demo/' directory contains example GPO files that, if applied, would compromise the victim machine (e.g., adding a guest user to Administrators, disabling UAC and firewall). The exploit requires the attacker to be in a MITM position and to know the victim's IP and the DC's DNS name. The attack vector is network-based, targeting Windows clients in Active Directory environments. No hardcoded IPs or domains are present, but the exploit is designed to be used in a lab or targeted environment where the attacker controls the network path.
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.
5 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.