dbcve.org
Virtual Raid On CpuApplication · Intel

CVE-2024-23489

HIGH · 7.3 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 8.6.0.1191 or later.
See remediation →
73/100
Remediation priority · Elevated

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
Uncontrolled search path for some Intel(R) VROC software before version 8.6.0.1191 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 before version 8.6.0.1191 contains an uncontrolled search path vulnerability that allows an authenticated local user to potentially achieve privilege escalation. An attacker could manipulate the application search path to load malicious code with elevated privileges.

MitigationUpdate Intel VROC software to version 8.6.0.1191 or later to remediate this 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.6.0.1191

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 VROC is installed
    Locate the Intel VROC software installation on the system. Check for VROC-related processes, services, or installed binaries. On Windows, check Program Files for Intel folders; on Linux, check /opt or /usr/bin for vroc components.
    Affected if Intel VROC software is present on the system
  2. Identify the installed VROC version
    Retrieve the version of the installed Intel VROC software. Common methods include checking file properties of the main executable, using the software's built-in version command, or querying the installed package information through the operating system's software management tools.
    Affected if The version cannot be determined or the software is found without a version number
  3. Compare version against the vulnerable range
    Compare the identified version number to the threshold 8.6.0.1191. Ensure the comparison accounts for major, minor, and build number components in the version string.
    Affected if The installed version is lower than 8.6.0.1191 (for example, 8.5.x, 8.4.x, or earlier)
  4. Verify if VROC service runs with elevated privileges
    Check the service account or process privileges under which the Intel VROC software runs. On Windows, use Services.msc or sc query to examine the service Log On As setting. On Linux, check the service configuration or process ownership.
    Affected if The VROC service runs under an account with administrator or root privileges

The system is affected if Intel VROC software is installed with a version lower than 8.6.0.1191 and runs with elevated privileges, allowing a local authenticated attacker to manipulate the search path for privilege escalation.

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.6.0.1191 or later
Fixed in 8.6.0.1191
Interim mitigation

Update Intel VROC software to version 8.6.0.1191 or later to remediate this vulnerability.

Recommended fix High confidence

8.6.0.1191

  1. 1. Identify the current Intel VROC version installed on the system through Device Manager or Intel's installation utility
  2. 2. Navigate to the official Intel support website or Intel's download center
  3. 3. Search for Intel VROC (Virtual RAID on CPU) software
  4. 4. Download the version 8.6.0.1191 or later from Intel's official download page
  5. 5. Run the installer with administrative privileges
  6. 6. Follow the on-screen installation wizard prompts to complete the upgrade
  7. 7. Restart the system as prompted to ensure the new driver/software loads properly
  8. 8. Verify the installed version matches 8.6.0.1191 or later after reboot
Caveat Driver updates may require system downtime and could affect RAID configurations if not performed according to Intel's upgrade documentation; backup RAID data before proceeding

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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