Nuc Pro Software SuiteApplication · Intel

CVE-2022-34855

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 2.0.0.3 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
Path traversal for the Intel(R) NUC Pro Software Suite before version 2.0.0.3 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

A path traversal vulnerability in Intel NUC Pro Software Suite before version 2.0.0.3 allows an authenticated user with local access to manipulate file paths and potentially escalate privileges. The vulnerability stems from insufficient input validation when handling file references, enabling attackers to escape restricted directories.

MitigationUpgrade Intel NUC Pro Software Suite to version 2.0.0.3 or later. Apply least-privilege principles to limit local user accounts and monitor for suspicious local access patterns.

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 Pro Software SuiteApplication
Affected:< 2.0.0.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
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. Confirm Intel NUC Pro Software Suite is installed
    Check for the software in the system registry under HKEY_LOCAL_MACHINE\SOFTWARE\Intel or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Intel, or look in standard installation directories like C:\Program Files\Intel or C:\Program Files (x86)\Intel
    Affected if The software is found on the system
  2. Determine the installed version
    Open the Windows registry key for Intel NUC Pro Software Suite and read the Version or DisplayVersion value, or right-click the application executable in Program Files and select Properties to view the File Version
    Affected if The version displayed is lower than 2.0.0.3 or cannot be determined to be 2.0.0.3 or later
  3. Verify local user access exists
    Check if local user accounts are present on the system by opening Computer Management > Local Users and Groups, or running 'net user' at the command prompt
    Affected if Local user accounts exist and the software accepts local authentication
  4. Confirm the software is running with elevated privileges
    Open Task Manager, locate the Intel NUC Pro Software Suite processes, right-click and select 'Run as administrator' status or check the process details for elevated token status
    Affected if The software runs with administrator or elevated privileges while permitting access from standard local user accounts

The system is affected if Intel NUC Pro Software Suite is installed with a version lower than 2.0.0.3 and local user authentication is enabled, allowing an authenticated local user to exploit the path traversal vulnerability.

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.0.0.3 or later
Fixed in 2.0.0.3
Interim mitigation

Upgrade Intel NUC Pro Software Suite to version 2.0.0.3 or later. Apply least-privilege principles to limit local user accounts and monitor for suspicious local access patterns.

Recommended fix High confidence

2.0.0.3

  1. Verify current installation version of Intel NUC Pro Software Suite
  2. If version is below 2.0.0.3, download the latest version from Intel's support website
  3. Close any running instances of the Intel NUC Pro Software Suite
  4. Install version 2.0.0.3 or later following standard installation procedures
  5. Restart the system if prompted
  6. Verify the installed version matches or exceeds 2.0.0.3

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

Fix this in Nuc Pro Software Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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