dbcve.org
Nuc Software Studio ServiceApplication · Intel

CVE-2022-38103

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 1.17.38.0 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
Insecure inherited permissions in the Intel(R) NUC Software Studio Service installer before version 1.17.38.0 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 · high confidence

The Intel NUC Software Studio Service installer before version 1.17.38.0 creates or modifies files/services with insecure inherited permissions. An authenticated local user can exploit these overly permissive file or service permissions to elevate their privileges on the system.

MitigationUpgrade Intel NUC Software Studio Service to version 1.17.38.0 or later to obtain the patched installer with corrected permission handling.

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
Nuc Software Studio ServiceApplication
Affected:< 1.17.38.0

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 NUC Software Studio Service is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Intel NUC Software Studio Service' in the list of installed programs.
    Affected if The software is not listed in installed programs, meaning the product is not present and not affected.
  2. Identify the installed version
    In Programs and Features, locate Intel NUC Software Studio Service and note the version column. Alternatively, check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry related to Intel NUC Software Studio.
    Affected if The version shown is lower than 1.17.38.0, indicating the vulnerable version is installed.
  3. Locate the service executable
    Open Services console (services.msc), find the Intel NUC Software Studio Service, right-click and select Properties, and note the path to the executable under 'Path to executable'.
    Affected if The service exists and points to a file in the Intel NUC Software Studio installation directory.
  4. Verify service file permissions
    Right-click the service executable file identified in the previous step, select Properties > Security tab, and examine the permissions. Look for overly broad permissions granted to non-admin users or Everyone group.
    Affected if Users without administrator privileges or the Everyone group have Modify, Write, or Full Control permissions on the service executable, creating an exploitable condition.

The system is affected if Intel NUC Software Studio Service is installed with a version prior to 1.17.38.0 and the service executable or related files have overly permissive access controls allowing unprivileged users to modify them.

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.17.38.0 or later
Fixed in 1.17.38.0
Interim mitigation

Upgrade Intel NUC Software Studio Service to version 1.17.38.0 or later to obtain the patched installer with corrected permission handling.

Recommended fix High confidence

1.17.38.0 or later

  1. 1. Check the currently installed version of Intel NUC Software Studio Service via Windows Control Panel > Programs and Features or by running 'appwiz.cpl'
  2. 2. If the installed version is earlier than 1.17.38.0, download the fixed version from the official Intel support website at www.intel.com
  3. 3. Completely uninstall the current version of NUC Software Studio Service through Windows Control Panel > Programs and Features
  4. 4. After uninstallation, verify that the service has been removed from the system
  5. 5. Run the installer for version 1.17.38.0 or later as an administrator
  6. 6. Follow the on-screen installation prompts to complete the installation
  7. 7. After installation, verify the installed version is 1.17.38.0 or higher and confirm the service is running properly
  8. 8. Verify that the installer permissions issue is resolved by checking that the service executable and related files have appropriate access controls

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

Fix this in Nuc Software Studio Service Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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