CVE-2025-20099
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 · uneditedImproper access control for some Intel(R) Rapid Storage Technology installation software 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 confidenceIntel Rapid Storage Technology installation software has improper access control that allows an authenticated local user to elevate their privileges. The vulnerability exists in the installation or configuration process of the software, where insufficient permission checks permit a non-privileged authenticated user to gain higher-level system access.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Intel Rapid Storage Technology is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Intel*Rapid*Storage*"}' in PowerShell. Look for any Intel Rapid Storage Technology or Intel RST entry.Affected if Intel Rapid Storage Technology software is present on the system.
-
Identify installed Intel RST versionIn Programs and Features, click on the Intel RST entry to view the version, or check the file version of C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorIcon.exe or similar executable in the install directory.Affected if The installed version falls within the vulnerable version range (prior to vendor patch).
-
Verify installation directory permissionsRight-click the Intel RST installation directory (typically C:\Program Files\Intel\Intel(R) Rapid Storage Technology), select Properties > Security, and check if non-privileged users have write or modify permissions.Affected if Authenticated non-admin users have elevated write/modify access to installation directories or configuration files.
-
Check for pending or recent installation activityReview Windows Event Viewer under Windows Logs > Application for MSI installer events related to Intel RST, or check C:\ProgramData\Intel\Logs for installation logs.Affected if Installation was performed without proper elevated privilege enforcement or logs indicate permission check failures.
The system is affected if Intel Rapid Storage Technology is installed with a vulnerable version AND non-privileged authenticated users can modify installation directories or trigger the installer without proper elevation.
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 dataApply the vendor-supplied patch or update to Intel Rapid Storage Technology installation software as provided by Intel. Verify that the update is applied to all affected systems in the enterprise.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20099 — 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-2025-20099 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