CVE-2021-0180
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 · uneditedUncontrolled resource consumption in the Intel(R) HAXM software before version 7.6.6 may allow an unauthenticated user to potentially enable privilege escalation 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 · moderate confidenceA vulnerability in Intel HAXM software before version 7.6.6 allows an unauthenticated user with local access to cause uncontrolled resource consumption, potentially leading to privilege escalation. The issue stems from insufficient controls on resource allocation that can be exploited to gain elevated privileges.
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.6.6CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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.
-
Check if Intel HAXM is installedLook for Intel HAXM in the list of installed programs via Control Panel > Programs and Features, or check common installation directories such as C:\Program Files\Intel\HAXM or C:\Program Files (x86)\Intel\HAXMAffected if Intel HAXM is present on the system
-
Determine the installed version of Intel HAXMRight-click on the Intel HAXM entry in Programs and Features and select Properties, then view the Details tab for the version information. Alternatively, locate the haxm.exe file in the installation directory, right-click, and select Properties to view version detailsAffected if The version displayed is less than 7.6.6
-
Verify HAXM service statusOpen Services (services.msc) and look for the Intel HAXM service, or run 'sc query haxm' from an elevated command promptAffected if The HAXM service is running or set to auto-start and the version is below 7.6.6
-
Check for active virtual machines using HAXMRun 'haxmcheck.exe' if available in the HAXM installation directory, or check for running Android emulator instances that rely on HAXM accelerationAffected if HAXM is actively allocated to virtual machines and the version is vulnerable
The system is affected if Intel HAXM is installed with a version lower than 7.6.6 and the HAXM service or virtual machine acceleration is in active use
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.6.6
Upgrade Intel HAXM to version 7.6.6 or later to remediate the vulnerability.
Intel HAXM 7.6.6 or later
- Identify the current version of Intel HAXM installed on the system
- Download Intel HAXM version 7.6.6 or later from the official Intel website or through your system's package manager
- Uninstall the existing vulnerable version of Intel HAXM
- Install the updated version 7.6.6 or later
- Verify the installation by confirming the installed version matches or exceeds 7.6.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0180 — 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-2021-0180 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