dbcve.org
Converged Security Management Engine FirmwareApplication · Intel

CVE-2022-36392

HIGH · 7.5 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 11.8.94 / 11.12.94 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 input validation in some firmware for Intel(R) AMT and Intel(R) Standard Manageability before versions 11.8.94, 11.12.94, 11.22.94, 12.0.93, 14.1.70, 15.0.45, and 16.1.27 in Intel (R) CSME may allow an unauthenticated user to potentially enable denial of service 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 · high confidence

Improper input validation in Intel CSME firmware for AMT and Standard Manageability allows unauthenticated remote attackers to potentially cause denial of service via network access. The vulnerability stems from insufficient validation of network-input data in the manageability firmware, which can be exploited without authentication.

MitigationUpdate Intel AMT/CSME firmware to version 11.8.94, 11.12.94, 11.22.94, 12.0.93, 14.1.70, 15.0.45, 16.1.27 or later. For enterprise deployments, use Intel Endpoint Management Assistant (EMA) or Intel Management Engine (ME) Creator for controlled firmware updates.

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
Converged Security Management Engine FirmwareApplication
Affected:< 11.12.94< 11.8.94< 12.0.93< 14.1.70>= 14.5.0, < 14.5.50< 15.0.45< 16.1.27

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify Intel AMT or Standard Manageability is enabled
    Check system BIOS/UEFI settings under Intel AMT or Management Engine (ME) configuration, or use the Intel ME Info tool (meinfo or intel_me_info) to query the manageability capability status
    Affected if AMT or Standard Manageability is in a disabled state - if disabled, the network-facing attack surface does not exist and the system is not affected
  2. Determine Intel CSME firmware version
    Use Intel CSME version detection tools such as 'meinfo' (Linux/Windows), Intel System Tools, or check via Windows Management Instrumentation (wmic /namespace:\\root\cimv2 PATH Win32_ComputerSystemProduct get UUID) combined with Intel firmware version utilities. On some systems, the version is visible in BIOS under 'Intel Management Engine' or 'Intel CSME' firmware version information
    Affected if The installed CSME firmware version falls within any of these vulnerable ranges: < 11.12.94, < 11.8.94, < 12.0.93, < 14.1.70, >= 14.5.0 but < 14.5.50, < 15.0.45, or < 16.1.27
  3. Confirm AMT network interface is accessible
    Verify that the Intel AMT network interface (typically ports 16992/16993 for HTTP/SOAP or 623 for SOL/IDER) is exposed on the network. Check system network configuration and firewall rules. Use 'netsh int ip show addresses' or similar tools to identify network bindings
    Affected if The AMT interface is network-accessible and the CSME firmware version is in the affected ranges listed above - this combination indicates the system is vulnerable to unauthenticated remote denial of service

A system is affected only if Intel AMT or Standard Manageability is enabled, the CSME firmware version is below any of the fixed versions (11.8.94, 11.12.94, 12.0.93, 14.1.70, 14.5.50, 15.0.45, or 16.1.27), and the AMT network interface is accessible.

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.94 / 11.12.94 / 12.0.93 or later
Fixed in 11.8.9411.12.9412.0.93
Interim mitigation

Update Intel AMT/CSME firmware to version 11.8.94, 11.12.94, 11.22.94, 12.0.93, 14.1.70, 15.0.45, 16.1.27 or later. For enterprise deployments, use Intel Endpoint Management Assistant (EMA) or Intel Management Engine (ME) Creator for controlled firmware updates.

Recommended fix High confidence

Upgrade to Intel CSME/AMT firmware version 11.22.94, 12.0.93, 14.1.70, 15.0.45, or 16.1.27 (depending on hardware platform)

  1. 1. Identify the Intel AMT/CSME version currently installed on the affected system by accessing the Intel Management Engine BIOS Extension (MEBx) or using the Intel Management and Discovery Tool.
  2. 2. Determine the correct firmware version for your specific Intel hardware platform by consulting the Intel CSME/AMT compatibility documentation.
  3. 3. Download the appropriate Intel CSME firmware update from the Intel Support website (support.intel.com) or your system OEM (Original Equipment Manufacturer).
  4. 4. Apply the firmware update using one of the following methods: via the Intel Management Engine (ME) Firmware Update Tool, through OEM-provided update utilities, or via Intel AMT remote provisioning if already configured.
  5. 5. After updating, verify the new firmware version is correctly installed by checking the ME version in MEBx or via the Intel Management and Discovery Tool.
  6. 6. Restart the system to ensure the firmware update is fully applied.
Caveat Firmware updates to Intel CSME are low-level and cannot be easily rolled back; ensure power stability during update; some enterprise environments may require specific OEM-signed firmware

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

Fix this in Converged Security Management Engine Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing6.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,100
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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