CVE-2024-27461
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 · uneditedIncorrect default permissions in software installer for Intel(R) MAS (GUI) may allow an authenticated user to potentially enable denial of service 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 confidenceThe Intel(R) MAS (GUI) installer sets incorrect default file permissions on installed components, allowing authenticated local users to modify or interfere with software files. This permission misconfiguration could enable a local authenticated attacker to cause denial of service by corrupting or manipulating application resources.
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< 2.5.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Intel MAS GUI is installedCheck for the presence of Intel Memory And Storage Tool GUI in the system registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the executable in Program Files (typically under Intel or Intel Corporation folders)Affected if The software is found installed on the system
-
Determine installed versionLocate the main Intel MAS GUI executable (commonly named IntelMAS.exe or similar) and check its version properties via right-click > Properties > Details, or query the Windows registry key for the installed versionAffected if The installed version is lower than 2.5.0 (compare your version against the affected range)
-
Inspect installation directory permissionsRight-click the Intel MAS GUI installation folder (typically in Program Files or Program Files x86 under Intel Corporation), select Properties > Security tab, and examine the permissions for Users and authenticated users groupsAffected if Users or authenticated users groups are granted Write or Modify permissions to the installation directory
-
Verify executable file permissionsCheck individual executable files in the Intel MAS installation folder by reviewing their Security permissions; look for whether non-administrator accounts have write access to .exe or .dll filesAffected if Non-administrator users have Write or Modify permissions on critical application executables or DLLs
You are affected if Intel Memory And Storage Tool GUI is installed with a version lower than 2.5.0 AND the installation directory or its files grant write/modify access to standard user accounts.
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.
dbcve · scoped2.5.0
Apply vendor-supplied patch for Intel MAS to correct default permissions; verify installed files have appropriate restrictive ACLs limiting write access to administrators only.
2.5.0 or later
- 1. Identify the currently installed version of Intel(R) MAS (GUI) on the system
- 2. Navigate to the official Intel website or Intel Support portal to download Intel Memory and Storage Tool (MAS) version 2.5.0 or later
- 3. Download the installer for the fixed version
- 4. Run the installer and follow the on-screen prompts to upgrade the software
- 5. Verify the installation completed successfully and confirm the new version is 2.5.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27461 — 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-27461 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