Virtual Raid On CpuApplication · Intel

CVE-2023-35003

HIGH · 7.8 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 8.0.8.1001 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 transversal in some Intel(R) VROC software before version 8.0.8.1001 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

A path traversal vulnerability in Intel VROC (Virtual RAID on CPU) software versions prior to 8.0.8.1001 allows an authenticated local user to manipulate file paths and potentially escalate privileges. The vulnerability requires local system access and valid authentication.

MitigationUpdate Intel VROC software to version 8.0.8.1001 or later to address the path traversal 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
Virtual Raid On CpuApplication
Affected:< 8.0.8.1001

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. Verify Intel VROC software is installed
    Check for Intel VROC installation via system inventory, installed programs list, or by looking for VROC-related services and binaries on the system
    Affected if Intel VROC software is not found on the system, the user is not affected by this CVE
  2. Determine installed VROC version
    Use system tools to query the installed Intel VROC version (such as checking the software version through the VROC management interface, installer information, or system package information)
    Affected if The installed version cannot be determined or the software is not present, further checks are not applicable
  3. Compare version against vulnerable range
    Compare the identified version number to the affected range: any version prior to 8.0.8.1001 is vulnerable
    Affected if Installed version is less than 8.0.8.1001 (for example, 8.0.7.x, 8.0.6.x, or earlier), the system is potentially affected by the path traversal vulnerability
  4. Confirm local authentication is enabled
    Verify that local user authentication for VROC is configured and accessible (since the vulnerability requires an authenticated local user)
    Affected if Local authentication is not configured or the VROC management interface is not accessible to local users, exploitation may not be possible despite the vulnerable version

A system is affected if Intel VROC software is installed with a version prior to 8.0.8.1001 and local authenticated access to VROC is available.

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 8.0.8.1001 or later
Fixed in 8.0.8.1001
Interim mitigation

Update Intel VROC software to version 8.0.8.1001 or later to address the path traversal vulnerability.

Recommended fix High confidence

8.0.8.1001

  1. Identify the current version of Intel VROC software installed on the system
  2. Navigate to the Intel website or support portal to download VROC version 8.0.8.1001 or later
  3. Verify the integrity of the downloaded package using checksums if provided
  4. Follow Intel's standard installation procedure for VROC software updates
  5. Restart the system if required by the update installation
  6. Confirm the updated version is 8.0.8.1001 or higher

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

Fix this in Virtual Raid On Cpu Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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