dbcve.org
Endpoint Management Assistant Configuration ToolApplication · Intel

CVE-2022-41610

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 1.0.4 / 2.4 or later.
See remediation →
57/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 authorization in Intel(R) EMA Configuration Tool before version 1.0.4 and Intel(R) MC before version 2.4 software may allow an authenticated user to potentially enable denial of service 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

Improper authorization in Intel(R) EMA Configuration Tool before version 1.0.4 and Intel(R) MC before version 2.4 allows an authenticated local user to potentially enable denial of service. This authorization logic flaw permits a locally authenticated attacker to trigger a condition causing the software to become unavailable or unresponsive.

MitigationUpgrade to Intel EMA Configuration Tool version 1.0.4 or later and Intel MC version 2.4 or later. Apply the principle of least privilege to local user accounts to limit exposure.

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
Endpoint Management Assistant Configuration ToolApplication
Affected:< 1.0.4
Manageability CommanderApplication
Affected:< 2.4

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Check if Intel EMA Configuration Tool is installed
    Look for the software in system-installed programs via Control Panel > Programs and Features, or check common installation directories such as C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\ for a folder named 'EMA Configuration Tool' or similar Intel EMA entries.
    Affected if The software is installed and its version is below 1.0.4
  2. Check if Intel Manageability Commander is installed
    Look for the software in system-installed programs via Control Panel > Programs and Features, or check common installation directories such as C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\ for a folder named 'Manageability Commander' or 'Intel MC'.
    Affected if The software is installed and its version is below 2.4
  3. Determine installed version of Intel EMA Configuration Tool
    If installed, locate the executable (typically named ema.exe, EMAConfigTool.exe, or similar in the installation folder) and check its version properties via right-click > Properties > Details, or use a command such as 'wmic product where "name like '%EMA%'" get version' or check the application's About/Help section.
    Affected if Version is present and less than 1.0.4
  4. Determine installed version of Intel Manageability Commander
    If installed, locate the executable (typically named mc.exe, ManageabilityCommander.exe, or similar in the installation folder) and check its version properties via right-click > Properties > Details, or use a command such as 'wmic product where "name like '%Manageability%'" get version' or check the application's About/Help section.
    Affected if Version is present and less than 2.4

The environment is affected if either Intel EMA Configuration Tool version below 1.0.4 or Intel Manageability Commander version below 2.4 is installed and the software allows local user authentication.

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 1.0.4 / 2.4 or later
Fixed in 1.0.42.4
Interim mitigation

Upgrade to Intel EMA Configuration Tool version 1.0.4 or later and Intel MC version 2.4 or later. Apply the principle of least privilege to local user accounts to limit exposure.

Recommended fix High confidence

Intel(R) Endpoint Management Assistant Configuration Tool version 1.0.4 or Intel(R) Manageability Commander version 2.4

  1. Identify which affected product is in use: Intel(R) Endpoint Management Assistant Configuration Tool or Intel(R) Manageability Commander
  2. For Endpoint Management Assistant Configuration Tool users: Locate and download version 1.0.4 or later from Intel's support website
  3. For Manageability Commander users: Locate and download version 2.4 or later from Intel's support website
  4. Backup any existing configurations or data before upgrading
  5. Stop the running service if applicable
  6. Install the upgraded version (1.0.4 for EMA Configuration Tool, or 2.4 for MC)
  7. Restart the service and verify the installation was successful
  8. Confirm the software version reflects the fixed release

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

Fix this in Endpoint Management Assistant Configuration Tool Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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