CVE-2024-22245
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedArbitrary Authentication Relay and Session Hijack vulnerabilities in the deprecated VMware Enhanced Authentication Plug-in (EAP) could allow a malicious actor that could trick a target domain user with EAP installed in their web browser into requesting and relaying service tickets for arbitrary Active Directory Service Principal Names (SPNs).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceVMware Enhanced Authentication Plug-in (EAP), now deprecated, contains authentication relay vulnerabilities allowing a remote attacker to trick authenticated users into requesting and relaying Kerberos service tickets for arbitrary Active Directory SPNs. This enables session hijacking and potential privilege escalation within the domain.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if VMware Enhanced Authentication Plug-in is installedOn Windows, open Control Panel > Programs and Features and search for 'VMware Enhanced Authentication Plug-in' or 'VMware EAP'. Alternatively, run 'Get-WmiObject -Class Win32_Product | Select-Object Name,Version' in PowerShell to list installed software.Affected if The plug-in appears in the installed programs list
-
Check browser extensions for EAP presenceIn Chrome, navigate to chrome://extensions and enable 'Developer mode' to view all extensions. In Firefox, go to about:addons. In Edge, navigate to edge://extensions. Look for any extension named 'VMware Enhanced Authentication Plug-in' or 'VMware EAP'.Affected if The VMware EAP browser extension is present and enabled
-
Verify if VMware EAP service or driver is loadedOn Windows, open Task Manager and check for processes named 'vmware-eap' or similar. Also run 'sc query' in command prompt to list services. On macOS, run 'ps aux | grep -i eap' in Terminal to check for running EAP processes.Affected if A VMware EAP process or service is running on the system
-
Check Windows registry for EAP installation entriesOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Search for registry keys containing 'VMware' and 'EAP' or 'Enhanced Authentication Plug-in'.Affected if Registry entries for VMware EAP are found
A system is affected if the VMware Enhanced Authentication Plug-in is installed, regardless of version, because the vulnerability exists in the deprecated plug-in itself and can enable Kerberos relay attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUninstall the deprecated VMware Enhanced Authentication Plug-in from all affected systems and browsers to eliminate the attack vector.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22245 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data