Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2014-6324: Kerberos Checksum Vulnerability

Published Nov 18, 2014 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS87.4%100th percentile
CISA KEVYesAdded Mar 25, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2014-6324CWE-347

CVE-2014-6324 is a signature-validation vulnerability in the Microsoft Windows Kerberos Key Distribution Center (KDC). A remote authenticated domain user can submit a Kerberos ticket with a forged signature to obtain domain administrator privileges. Affected versions include Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and 2008 R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, and Windows Server 2012 and 2012 R2. The vulnerability was exploited in the wild in November 2014 and addressed by Microsoft security bulletin MS14-068.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unprivileged domain user can escalate to domain administrator, enabling full compromise of domain computers, including domain controllers. The resulting privileges permit access to sensitive domain resources, administrative changes, and lateral movement throughout the affected domain.

Mitigation

If you can’t patch tonight, do this now.

Until the update is deployed, restrict access to domain controllers and monitor for suspicious Kerberos ticket activity. Access restrictions reduce exposure but do not correct the signature-validation flaw.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update identified in MS14-068 to all affected systems, prioritizing domain controllers.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Server 2003operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
FAQ

Frequently asked questions

Is CVE-2014-6324 exploited in the wild?
Yes. As of Nov 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 25, 2022.
Is there a public exploit for CVE-2014-6324?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2014-6324, the earliest disclosed Nov 18, 2014.
Is there a patch for CVE-2014-6324?
Apply the Microsoft security update identified in MS14-068 to all affected systems, prioritizing domain controllers.
What products are affected by CVE-2014-6324?
Microsoft Corporation Windows 7, Microsoft Corporation Windows 8, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Server 2003, Microsoft Corporation Windows Server 2008, and 1 more.
How severe is CVE-2014-6324?
CVE-2014-6324 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 87.4% (100th percentile) as of Nov 9, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence7Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures4YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.