dbcve.org
Virtual Raid On CpuApplication · Intel

CVE-2023-34315

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
Incorrect default permissions 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 · high confidence

Intel VROC (Virtual RAID on CPU) software versions before 8.0.8.1001 ship with incorrect default file system permissions that allow an authenticated local user to gain elevated privileges. This is a privilege escalation vulnerability stemming from overly permissive access controls on software components.

MitigationUpgrade Intel VROC software to version 8.0.8.1001 or later to obtain corrected default permissions. Alternatively, manually audit and restrict file/folder permissions on the VROC installation directory to follow least-privilege principles.

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 is installed
    Check for the presence of Intel VROC software by looking in the Windows Registry under HKLM\SOFTWARE\Intel\VROC or by searching for 'Intel Virtual RAID on CPU' in Add/Remove Programs. Alternatively, check for the VROC installation folder in Program Files (typically C:\Program Files\Intel\VROC or similar).
    Affected if Intel VROC software is found installed on the system
  2. Determine the installed VROC version
    Locate the VROC installation directory and check for version information in the file properties of the main executable (often named VROC* or stored in an About/Version file), or query the Windows Registry key where the version is stored (commonly under the same path where the product is registered).
    Affected if The installed version is lower than 8.0.8.1001 or the version cannot be determined (treat unknown versions as potentially vulnerable)
  3. Audit file system permissions on the VROC installation folder
    Right-click the VROC installation folder, go to Properties > Security, and examine the permissions for Users and Authenticated Users groups. Specifically check if these groups have Write, Modify, or Full Control permissions on critical subfolders (especially those containing executables, configuration files, or drivers).
    Affected if Authenticated users or the Users group have Write, Modify, or Full Control permissions on VROC executable or configuration directories

The system is affected if Intel VROC version is present and is lower than 8.0.8.1001, or if the VROC installation directory grants overly permissive access to standard user accounts.

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

Upgrade Intel VROC software to version 8.0.8.1001 or later to obtain corrected default permissions. Alternatively, manually audit and restrict file/folder permissions on the VROC installation directory to follow least-privilege principles.

Recommended fix Moderate confidence

8.0.8.1001

  1. Identify the current Intel VROC software version installed on the system
  2. Download Intel VROC software version 8.0.8.1001 or later from the official Intel website (support.intel.com)
  3. Review Intel VROC release notes for version 8.0.8.1001 to understand changes and requirements
  4. Ensure proper backups are in place before applying the update
  5. Apply the Intel VROC software upgrade following Intel's installation documentation
  6. Verify the installed version is 8.0.8.1001 or later after upgrade completes
  7. Confirm the VROC functionality is operating normally after the update

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

Fix this in Virtual Raid On Cpu 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-2023-34315 — 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-34315 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