dbcve.org
Sandisk Professional G Raid 4\/8 Software UtilityApplication · Westerndigital

CVE-2022-22996

HIGH · 7.8 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to 6.2.0.16-2 / 300520006-2 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
The G-RAID 4/8 Software Utility setups for Windows were affected by a DLL hijacking vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the system user.

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

The G-RAID 4/8 Software Utility installer for Windows is vulnerable to DLL hijacking, where the application loads attacker-controlled DLLs from insecure paths. This allows execution of arbitrary code with the privileges of the user running the installer, typically a system administrator during setup.

MitigationUsers should obtain the software exclusively from official vendor sources and ensure the installer runs from a trusted directory. The vendor must patch the installer to use secure DLL loading practices (e.g., SetDllDirectory, explicit DLL paths, or secure search order).

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
Sandisk Professional G Raid 4\/8 Software UtilityApplication
Affected:< 300520006-2
Sandisk Professional G Raid 4\/8 Software Utility DriverApplication
Affected:< 6.2.0.16-2

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

CVSS:3.1/AV:L/AC:L/PR:N/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. Locate the G-RAID Software Utility installation
    Open Programs and Features (appwiz.cpl) or use 'Get-ItemProperty' in PowerShell to find installed programs matching 'G-RAID' or 'Western Digital' storage utilities
    Affected if The application is listed as installed on the system
  2. Identify the installed software version
    Right-click the G-RAID entry in Programs and Features and select Properties, or use: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*G-RAID*'} | Select-Object DisplayName, DisplayVersion
    Affected if The displayed version is below 300520006-2
  3. Identify the installed driver version (if present)
    Open Device Manager, expand 'Disk drives' or 'Storage controllers', look for G-RAID devices, right-click and select Properties > Driver tab. Alternatively, run: driverquery /v | findstr -i g-raid
    Affected if The driver version displayed is below 6.2.0.16-2 or the driver is present but version cannot be determined
  4. Confirm vulnerable DLL loading path condition
    Review the installer behavior: if the installer runs from a user-controlled or network directory rather than a trusted local path, the DLL hijacking can be exploited. Check the directory from which the installer was originally run.
    Affected if The installer was executed from a directory with write access by non-admin users (such as Downloads or network shares)

A system is affected if either the G-RAID Software Utility version is below 300520006-2 or the G-RAID Driver version is below 6.2.0.16-2, and the installer was run from an insecure directory path.

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 6.2.0.16-2 / 300520006-2 or later
Fixed in 6.2.0.16-2300520006-2
Interim mitigation

Users should obtain the software exclusively from official vendor sources and ensure the installer runs from a trusted directory. The vendor must patch the installer to use secure DLL loading practices (e.g., SetDllDirectory, explicit DLL paths, or secure search order).

Recommended fix Moderate confidence

G-RAID 4/8 Software Utility version 300520006-2 and Driver version 6.2.0.16-2 (or later) from Western Digital

  1. Check current version of G-RAID 4/8 Software Utility by opening the application and navigating to Help > About
  2. Check current version of G-RAID 4/8 Software Utility Driver via Windows Device Manager under the driver properties
  3. Navigate to the Western Digital support website at www.westerndigital.com to download the latest version
  4. Download and install G-RAID 4/8 Software Utility version 300520006-2 or later
  5. Download and install G-RAID 4/8 Software Utility Driver version 6.2.0.16-2 or later
  6. Restart the system after updating both components
  7. Verify the installed versions match or exceed the fixed releases

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

Fix this in Sandisk Professional G Raid 4\/8 Software Utility Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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