Manageability CommanderApplication · Intel

CVE-2022-29887

CRITICAL · 9.6 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-site Scripting (XSS) in some Intel(R) Manageability Commander software before version 2.3 may allow an unauthenticated 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 · high confidence

A stored Cross-site Scripting (XSS) vulnerability exists in the web interface of Intel(R) Manageability Commander software versions prior to 2.3. An unauthenticated attacker can inject malicious scripts through the interface that execute in other users' browsers, potentially leading to session hijacking and privilege escalation.

MitigationUpgrade Intel Manageability Commander to version 2.3 or later to remediate this vulnerability.

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
Manageability CommanderApplication
Affected:< 2.3

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Confirm Intel Manageability Commander is installed
    Check system for Intel Manageability Commander installation directories or running services (typically installed under Program Files or similar locations)
    Affected if The software is present on the system
  2. Identify installed version
    Locate version information in the software installation directory, help/about dialog, or installed programs list
    Affected if Version is present but shows a number lower than 2.3 (e.g., 2.2, 2.1, 2.0, etc.)
  3. Verify web interface is accessible
    Check if the Intel Manageability Commander web service is running and the web interface port is open (common ports include 8080, 8443, or as configured during setup)
    Affected if The web interface is enabled and reachable on the network or locally
  4. Compare version to affected range
    Review the installed version against the affected range: versions prior to 2.3 are vulnerable
    Affected if Installed version is any release before 2.3 (e.g., 2.2.x, 2.1.x, 2.0.x)
  5. Check for recent security updates
    Look for version 2.3 or later in the installed software, or check Intel support pages for the software version history
    Affected if Version 2.3 or later is NOT installed and the web interface is in use

The system is affected if Intel Manageability Commander is installed with a version number lower than 2.3 and the web interface is enabled and 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 2.3 or later
Fixed in 2.3
Interim mitigation

Upgrade Intel Manageability Commander to version 2.3 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Intel Manageability Commander version 2.3

  1. Back up any existing Intel Manageability Commander configuration data
  2. Download Intel Manageability Commander version 2.3 or later from the official Intel support website
  3. Stop the Intel Manageability Commander service if currently running
  4. Install the version 2.3 package using the standard installation procedure
  5. Restart the Intel Manageability Commander service
  6. Verify the installed version is 2.3 or later

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

Fix this in Manageability Commander Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29887 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