dbcve.org
Virtual Raid On CpuApplication · Intel

CVE-2022-30338

HIGH · 7.8 CVSS v3.1 Published 2023-05-10
Fix available
A fix is available. Upgrade to 7.7.6.1003 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 the Intel(R) VROC software before version 7.7.6.1003 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

Intel VROC (Virtual RAID on CPU) software before version 7.7.6.1003 ships with incorrect default permissions on certain files or directories that allow an authenticated local user to modify protected resources and escalate privileges to a higher permission level.

MitigationUpgrade Intel VROC software to version 7.7.6.1003 or later to obtain the corrected default permissions. Verify that the installed version meets this minimum requirement.

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:< 7.7.6.1003

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 if Intel Virtual RAID on CPU (VROC) software is present on the system. On Windows, look in Programs and Features or check for VROC-related services. On Linux, check for VROC packages via package manager (rpm, dpkg) or look for VROC installation directories.
    Affected if Intel VROC software is found installed on the system
  2. Identify the installed VROC version
    Locate the VROC version information. On Windows, this is typically available in Programs and Features, or check the VROC driver/software properties. On Linux, check /opt/intel/vroc or similar installation directories for version files, or use: rpm -qa | grep vroc or dpkg -l | grep vroc.
    Affected if The installed version is lower than 7.7.6.1003
  3. Check for vulnerable file or directory permissions
    Examine permissions on VROC installation directories and files. Typical locations include C:\Program Files\Intel\VROC (Windows) or /opt/intel/vroc (Linux). Use icacls (Windows) or ls -la (Linux) to view ACLs. Look for directories or files that grant write or modify access to standard users or Authenticated Users groups.
    Affected if Any VROC-related files or directories show overly permissive ACLs (such as Everyone, Users, or Authenticated Users with write/modify rights)
  4. Verify local user access context
    Confirm that the system allows local authenticated users to access the VROC installation directories. Check if non-privileged local accounts exist and can navigate to or modify VROC files.
    Affected if Local authenticated users have access to VROC directories with weak permissions

If Intel VROC is installed with a version lower than 7.7.6.1003 and the installation directories have permissive ACLs allowing standard users to modify files, the environment is affected by this privilege escalation 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 7.7.6.1003 or later
Fixed in 7.7.6.1003
Interim mitigation

Upgrade Intel VROC software to version 7.7.6.1003 or later to obtain the corrected default permissions. Verify that the installed version meets this minimum requirement.

Recommended fix Moderate confidence

7.7.6.1003 or later

  1. Identify the current version of Intel VROC software installed on the system
  2. Navigate to Intel's official support website or download page for VROC software
  3. Locate and download Intel VROC version 7.7.6.1003 or a later stable release
  4. Follow Intel's standard upgrade procedure for VROC software, which typically involves running the installer with appropriate administrative privileges
  5. Reboot the system as required by the installation process
  6. Verify the installed VROC version is 7.7.6.1003 or later

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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