dbcve.org
Active Management Technology FirmwareOperating system · Intel

CVE-2022-29893

HIGH · 8.8 CVSS v3.1 Published 2022-11-11
Fix available
A fix is available. Upgrade to 11.8.93 / 11.12.93 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 authentication in firmware for Intel(R) AMT before versions 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, 16.1.25 may allow an authenticated user to potentially enable escalation of privilege via network 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

Improper authentication in Intel(R) AMT firmware allows an authenticated user to escalate privileges via network access. The vulnerability stems from insufficient authentication controls in the AMT subsystem, enabling a user with valid credentials to gain higher-level access than intended.

MitigationUpdate Intel AMT firmware to versions 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, or 16.1.25 or later. Prioritize systems with network-accessible AMT interfaces.

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
Active Management Technology FirmwareOperating system
Affected:< 11.8.93>= 11.12.0, < 11.12.93>= 11.22.0, < 11.22.93>= 12.0, < 12.0.92>= 14.1, < 14.1.67>= 15.0, < 15.0.42>= 16.1.0, < 16.1.25

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

CVSS:3.1/AV:N/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 checks

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

  1. Check if Intel AMT is present and enabled
    On Windows, run 'wmic /namespace:\\root\cimv2\intel_me path Win32_ComputerSystem get Manufacturer,Model' and check BIOS/UEFI for Intel AMT or Intel ME entries. On Linux, check 'cat /sys/class/dmi/id/board_vendor' and look for AMT indicators in dmesg or system logs.
    Affected if Intel AMT or Intel Management Engine is found to be present and enabled on the system
  2. Retrieve the Intel AMT firmware version
    Access the Intel AMT Web Interface by navigating to https://hostname:16992 or https://hostname:16993 (if enabled), or use the Intel ME BIOS Extension (MEBX) during boot to view the AMT firmware version. On Windows, you may also use 'wmic /namespace:\\root\cimv2\intel_me path Intel_AMT_Instance get MajorVersion,MinorVersion' or check the Intel Management Engine BIOS Extension version shown at boot.
    Affected if Unable to retrieve the version indicates AMT may not be accessible or configured, but if version is retrieved proceed to next check
  3. Compare installed version against affected ranges
    Interpret the retrieved version number (for example, version 11.22.50 translates to 11.22.50). Check if it falls into any of these ranges: < 11.8.93; >= 11.12.0 and < 11.12.93; >= 11.22.0 and < 11.22.93; >= 12.0 and < 12.0.92; >= 14.1 and < 14.1.67; >= 15.0 and < 15.0.42; >= 16.1.0 and < 16.1.25.
    Affected if The installed Intel AMT firmware version falls within any of the affected version ranges listed
  4. Verify AMT network accessibility
    Check if ports 16992 (HTTP) or 16993 (HTTPS) are listening and accessible on the network by running 'netstat -an | findstr 1699' on Windows or 'ss -tlnp | grep 1699' on Linux. Confirm the AMT interface is configured for network access rather than only local access.
    Affected if Intel AMT is network-accessible (listening on ports 16992/16993) and the firmware version is in the affected ranges, making exploitation feasible over the network

The system is affected if Intel AMT firmware is present, enabled, network-accessible, and the installed version falls within any of the listed vulnerable version ranges.

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.

dbcve · scoped
Upgrade available Upgrade to 11.8.93 / 11.12.93 / 11.22.93 or later
Fixed in 11.8.9311.12.9311.22.93
Interim mitigation

Update Intel AMT firmware to versions 11.8.93, 11.22.93, 11.12.93, 12.0.92, 14.1.67, 15.0.42, or 16.1.25 or later. Prioritize systems with network-accessible AMT interfaces.

Recommended fix High confidence

Upgrade to version 11.8.93, 11.12.93, 11.22.93, or 12.0.92 (or later) depending on your current version branch; for branches 14.x, 15.x, and 16.x upgrade to 14.1.67, 15.0.42, and 16.1.25 respectively

  1. Identify the current Intel AMT firmware version on affected systems using the Intel Management Engine BIOS Extension (MEBX) or Intel SCS/WSUS inventory
  2. Determine which version branch is currently in use (11.8.x, 11.12.x, 11.22.x, or 12.0.x)
  3. Download the appropriate Intel AMT firmware update from Intel's support site or through the Intel Endpoint Management Assistant (EMA) / Intel Setup and Configuration Software (SCS)
  4. Apply the firmware update through the Intel AMT firmware deployment mechanism (e.g., Intel SCS, Microsoft WS-SUS, or direct firmware flash)
  5. Verify the firmware has been updated to the correct fixed version (11.8.93, 11.12.93, 11.22.93, or 12.0.92 or later)
  6. Confirm Intel AMT is functioning normally post-update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Active Management Technology Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29893 — 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-29893 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