CVE-2022-21812
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 · uneditedImproper access control in the Intel(R) HAXM software before version 7.7.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
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 · high confidenceIntel HAXM (Hardware Accelerated Execution Manager) before version 7.7.1 contains an improper access control vulnerability that allows an authenticated local user to escalate privileges. This is a local privilege escalation issue in the virtualization software that Intel provides for running Android emulators faster.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.7.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.
-
Locate Intel HAXM installationSearch for the Intel HAXM executable or service. Common locations include C:\Program Files\Intel\HAXM\ or check for the haxm.exe service. On Linux, check /usr/lib/haxm/ or /opt/intel/haxm/. Also verify via Windows Services or running 'sc query haxm' command.Affected if Intel HAXM software is present on the system
-
Determine installed HAXM versionRun 'haxm.exe -version' from the installation directory, or right-click haxm.exe and select Properties > Details to view the File Version. On Windows, you can also check via 'sc qc haxm' or in Add/Remove Programs.Affected if Version cannot be determined or is less than 7.7.1
-
Verify version against affected rangeCompare the detected version number to the vulnerable threshold: any version before 7.7.1 is affected. Note that version 7.7.1 itself is not affected.Affected if Installed version is 7.7.0 or earlier, or any pre-7.7.1 release
-
Confirm HAXM service or driver is activeCheck if the HAXM hypervisor is loaded. On Windows, run 'sc query haxm' or check Device Manager for Intel Hardware Accelerated Execution Manager. On Linux, check 'lsmod | grep haxm' or 'kvm -accel' status.Affected if HAXM service or driver is running (prerequisite for the privilege escalation to be exploitable)
If Intel HAXM is installed with a version earlier than 7.7.1 and the service is active, the system is vulnerable to local privilege escalation via this CVE.
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.
dbcve · scoped7.7.1
Upgrade Intel HAXM to version 7.7.1 or later to address the improper access control vulnerability.
7.7.1
- Download Intel HAXM version 7.7.1 or later from the official Intel website or your system's software update mechanism
- Uninstall the current version of Intel HAXM if already installed
- Install the updated Intel HAXM version 7.7.1
- Verify the installation by checking the installed version matches or exceeds 7.7.1
- Restart any emulators or virtual machines that rely on HAXM to ensure the new version is properly initialized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21812 — 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-2022-21812 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