CVE-2024-22002
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 · uneditedCORSAIR iCUE 5.9.105 with iCUE Murals on Windows allows unprivileged users to insert DLL files in the cuepkg-1.2.6 subdirectory of the installation directory.
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 confidenceCORSAIR iCUE 5.9.105 with iCUE Murals on Windows contains a DLL hijacking vulnerability where unprivileged users can insert arbitrary DLL files into the cuepkg-1.2.6 subdirectory of the installation directory. When the privileged iCUE application loads, it may execute these malicious DLLs, potentially leading to local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify iCUE installation and versionCheck for CORSAIR iCUE installation in Program Files or Program Files (x86), typically under 'Corsair\CORSAIR iCUE'. Retrieve the version from the iCUE.exe file properties or check the installed version via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{iCUE Product ID}Affected if iCUE version 5.9.105 with iCUE Murals is installed
-
Confirm cuepkg-1.2.6 subdirectory existsNavigate to the iCUE installation directory and verify the presence of the 'cuepkg-1.2.6' subfolder. Common path: C:\Program Files\Corsair\CORSAIR iCUE\cuepkg-1.2.6Affected if The cuepkg-1.2.6 subdirectory exists in the iCUE installation folder
-
Inspect folder permissions on cuepkg-1.2.6Right-click the cuepkg-1.2.6 folder, go to Properties > Security tab, and review the granted permissions. Use 'icacls cuepkg-1.2.6' command to list effective permissions for all users and groupsAffected if Non-admin users or standard users have Write or Full Control permissions to this directory
-
Scan for unexpected DLL files in cuepkg-1.2.6List all .dll files in the cuepkg-1.2.6 directory using 'dir /b C:\Path\To\cuepkg-1.2.6\*.dll' or File Explorer. Compare against expected DLLs for this componentAffected if There are DLL files present that were not originally part of the iCUE installation or that match known malicious DLL patterns
A user is affected if they have iCUE version 5.9.105 installed AND non-administrative accounts have Write access to the cuepkg-1.2.6 subdirectory, allowing potential DLL planting for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict write permissions on the iCUE installation directory, specifically the cuepkg-1.2.6 subdirectory, to prevent unprivileged users from planting malicious DLL files. Only administrators or SYSTEM should have write access to these locations.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22002 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-22002 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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