dbcve.org
Core I7 11850he FirmwareOperating system · Intel

CVE-2022-30704

MEDIUM · 6.7 CVSS v3.1 Published 2023-02-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper initialization in the Intel(R) TXT SINIT ACM for some Intel(R) Processors may allow a privileged 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 · moderate confidence

This vulnerability in Intel(R) TXT SINIT ACM (Authenticated Code Module) involves improper initialization that could allow a locally-accessible privileged user to escalate their privileges. Intel TXT is a hardware-based security technology that creates a measured execution environment, and the initialization flaw in the SINIT ACM could be exploited to gain additional privileges beyond what the attacker initially possesses.

MitigationApply the appropriate Intel firmware/BIOS update for affected processors that addresses the SINIT ACM initialization issue. Organizations should verify their Intel TXT configuration and ensure only authorized administrators have access to TXT-protected environments.

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
Core I7 11850he FirmwareOperating system
Affected:all versions
Core I7 11600h FirmwareOperating system
Affected:all versions
Core I7 11390h FirmwareOperating system
Affected:all versions
Core I7 1195g7 FirmwareOperating system
Affected:all versions
Core I7 11800h FirmwareOperating system
Affected:all versions
Core I7 11850h FirmwareOperating system
Affected:all versions
Core I7 11700 FirmwareOperating system
Affected:all versions
Core I7 11700f FirmwareOperating system
Affected:all versions

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor model
    Run 'wmic cpu get name' on Windows or 'cat /proc/cpuinfo' on Linux to identify the exact CPU model. Look for the specific processor family listed in the affected products.
    Affected if The processor is one of: Intel Core i7-11850he, i7-11600h, i7-11390h, i7-1195g7, i7-11800h, i7-11850h, i7-11700, or i7-11700f.
  2. Check if Intel TXT is enabled in firmware settings
    Access the system BIOS/UEFI setup during boot (typically press Del, F2, or F12). Navigate to Security or Advanced settings and look for Intel TXT (Trusted Execution Technology) or Intel VT-d settings. Record whether TXT is currently enabled or disabled.
    Affected if Intel TXT is enabled in the BIOS/UEFI firmware.
  3. Verify TXT configuration status from operating system
    On Windows, use the Intel TXT hardware check tool or run 'msinfo32' and look for 'Intel(R) TXT'. On Linux, check /sys/class/tpm/ or use 'txt-stat' from the tboot package if available. Confirm whether TXT is reported as enabled or capable.
    Affected if The system reports Intel TXT as enabled or available.
  4. Check SINIT ACM firmware version if accessible
    On systems with tboot installed, run 'txt-stat' or examine /boot/tboot* files for SINIT ACM version information. Some enterprise tools may expose the ACM version through system management interfaces.
    Affected if The SINIT ACM version is earlier than the fixed version provided by Intel firmware updates.

You are affected if your system uses one of the listed Intel Core i7 processor models and has Intel TXT enabled in BIOS/UEFI firmware, as the vulnerability exists in the SINIT ACM component used by TXT.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Intel firmware/BIOS update for affected processors that addresses the SINIT ACM initialization issue. Organizations should verify their Intel TXT configuration and ensure only authorized administrators have access to TXT-protected environments.

Fix this in Core I7 11850he Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30704 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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