CVE-2024-28170
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 in Intel(R) RAID Web Console all versions may allow an authenticated user to potentially enable information disclosure 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 confidenceImproper access control in Intel(R) RAID Web Console allows authenticated users to potentially enable information disclosure via local access. The vulnerability stems from insufficient authorization checks that permit authenticated users to access information they should not have permission to view.
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 dataall versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 Intel RAID Web Console installationCheck for Intel RAID Web Console software on the system. On Windows, look in Program Files for 'Intel RAID Web Console' or check Programs and Features. On Linux, check for RPM/DEB packages named ' raid-web-console' or similar using 'rpm -qa' or 'dpkg -l'. Also check if the web service executable (often named 'RWCWeb' or similar) exists in common installation directories.Affected if Intel RAID Web Console software is found installed on the system
-
Confirm the web console service is runningCheck if the Intel RAID Web Console service or process is active. On Windows, open Services.msc and look for 'Intel RAID Web Console' service, or run 'Get-Service | Where-Object {$_.Name -like '*RAID*' -or $_.DisplayName -like '*RAID*'}' in PowerShell. On Linux, check running processes for the web console daemon.Affected if The Intel RAID Web Console service or process is currently running
-
Identify configured user accountsReview user accounts that have access to the RAID Web Console. Check the application's user configuration files, which may be located in the installation directory (often under a 'config' or 'users' subdirectory), or check the Windows local users/group settings if integrated with OS authentication. Look for any non-administrator accounts configured.Affected if Multiple user accounts or any authenticated user accounts are configured with access to the web console
-
Assess local access exposureDetermine if the system hosting the RAID Web Console can be accessed by unauthorized local users. Check physical access controls, console login permissions, and whether shared/local user sessions exist on the system. Review who has local login rights to the machine where the web console is hosted.Affected if The system running RAID Web Console is accessible to users beyond the intended administrators, or multiple users have local account access
If Intel RAID Web Console is installed, running, has user accounts configured, and the host system allows local access to additional users beyond the intended administrators, the environment is affected by this improper access control vulnerability.
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 vendor-provided patches for Intel RAID Web Console when available. Until a patch is released, implement least-privilege access controls and limit local system access to only essential, authorized personnel.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28170 — 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-28170 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