LiveActive security incident?Get immediate response
CVE Record

CVE-2022-21812: Improper access control in the Intel(R) HAXM software before version 7.7.1 may allow an authenticated user...

Improper 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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-21812 is a local privilege escalation issue in Intel HAXM before version 7.7.1. A user who already has local authenticated access could potentially gain higher privileges on the affected host. This is most urgent where untrusted or lightly trusted users can sign in to systems running HAXM.

Executive priority

Prioritize remediation for shared workstations, build systems, lab machines, and any host where non-administrators can log in. The business risk is local account compromise escalating into full host compromise, but the issue is not evidenced as remotely exploitable from the supplied sources.

Technical view

The issue is improper access control in Intel HAXM software before 7.7.1. The CVSS 3.1 score is 7.8 with local attack vector, low complexity, low privileges required, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to hosts running Intel HAXM before version 7.7.1. The source bundle does not identify default installations, bundled distributions, operating-system scope, or downstream products, so asset inventory is required to confirm exposure.

Exploitation context

The vulnerability requires authenticated local access. The provided sources do not show public exploitation, and the CVE is not marked in KEV. Treat it as a serious post-login escalation risk rather than a remote-entry vulnerability.

Researcher notes

Key unknowns are installation prevalence, platform-specific behavior, and whether proof-of-concept details exist outside the supplied bundle. The CVSS vector supports high impact after local authenticated access. Avoid claiming exploitation in the wild without KEV or another cited source.

Mitigation direction

  • Inventory systems for Intel HAXM installations and recorded versions.
  • Upgrade Intel HAXM to version 7.7.1 or later where still required.
  • Remove Intel HAXM from systems that no longer need it.
  • Restrict local access on affected hosts until remediation is complete.
  • Check Intel advisory INTEL-SA-00655 for current vendor guidance.

Validation and detection

  • Confirm every HAXM installation reports version 7.7.1 or later.
  • Verify no affected HAXM versions remain on shared or multi-user hosts.
  • Review endpoint software inventory for unmanaged or stale HAXM installs.
  • Confirm compensating access controls for any host awaiting remediation.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-21812 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-21812Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aIntel(R) HAXM softwarebefore version 7.7.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.