dbcve.org
Setup And Configuration SoftwareApplication · Intel

CVE-2023-22440

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to after 2.1.9 or later.
See remediation →
80/100
Remediation priority · High
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
Incorrect default permissions in the Intel(R) SCS Add-on software installer for Microsoft SCCM all versions may allow an authenticated 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

The Intel(R) SCS Add-on software installer for Microsoft SCCM sets incorrect default permissions on installed files or directories, allowing an authenticated local user to modify resources they should not have access to, leading to privilege escalation.

MitigationApply the Intel vendor patch/update when available to obtain an installer with correct permissions; otherwise, manually audit and correct file/directory permissions on the affected SCCM add-on installation to remove excessive user access rights.

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
Setup And Configuration SoftwareApplication
Affected:<= 2.1.9

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 SCS Add-on for SCCM is installed
    Look for Intel Setup And Configuration Software installation directory in typical locations such as 'C:\Program Files\Intel\Intel(R) SCS Add-on for Microsoft SCCM' or 'C:\Program Files (x86)\Intel\Intel(R) SCS Add-on for Microsoft SCCM'. Also check Add/Remove Programs or Programs and Features for Intel SCS Add-on entry.
    Affected if The Intel SCS Add-on for Microsoft SCCM is present on the system
  2. Identify the installed Intel SCS version
    Right-click on the main Intel SCS executable (typically named ISCSCCM.exe or similar in the installation folder) and select Properties, then check the Details tab for the File Version. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Intel\SetupAndConfigurationSoftware for a Version value.
    Affected if The installed version is 2.1.9 or earlier
  3. Audit permissions on Intel SCS installation directory
    Right-click the Intel SCS Add-on installation folder, select Properties, then go to the Security tab. Check which users and groups have permissions, particularly looking for Full Control or Modify permissions granted to authenticated users or non-admin users.
    Affected if Non-administrative users have Full Control or Modify permissions on files or subdirectories that should be restricted to administrators only

The system is affected if Intel SCS Add-on for Microsoft SCCM is installed with version 2.1.9 or earlier AND non-privileged users have excessive permissions on the installation directory.

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 a release after 2.1.9
Interim mitigation

Apply the Intel vendor patch/update when available to obtain an installer with correct permissions; otherwise, manually audit and correct file/directory permissions on the affected SCCM add-on installation to remove excessive user access rights.

Recommended fix Moderate confidence

Intel(R) SCS Add-on for Microsoft SCCM version > 2.1.9 (consult Intel advisory for exact fixed version)

  1. Identify the current version of Intel(R) SCS Add-on software for Microsoft SCCM installed in the environment
  2. Navigate to the Intel Security Advisory page for CVE-2023-22440 at www.intel.com
  3. Download the latest version of Intel(R) SCS Add-on software for Microsoft SCCM (version greater than 2.1.9)
  4. Verify the SHA256 checksum of the downloaded installer against the values provided in the Intel advisory
  5. Deploy the updated installer through Microsoft SCCM following standard deployment procedures
  6. Verify that the new version is installed and running without errors
  7. Confirm that the default permissions on installed files and directories are correctly set according to Intel's documentation

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

Fix this in Setup And Configuration Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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