CVE-2025-36511
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 for some Intel(R) Memory and Storage Tool before version 2.5.2 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
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 · high confidenceIntel(R) Memory and Storage Tool before version 2.5.2 contains incorrect default permissions that allow a local authenticated user to potentially escalate privileges from Ring 3 (user mode) to higher privileges. The vulnerability requires a high-complexity attack with active user interaction.
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.
-
Locate Intel Memory and Storage Tool executableSearch for the IntelMAS.exe or IntelMemoryAndStorageTool.exe executable in common installation directories such as Program Files\Intel\ or use the system search functionality to find the executable on the systemAffected if The executable is not found on the system, meaning the product is not installed
-
Retrieve installed version informationRight-click the located executable, select Properties, and view the Details tab to obtain the File Version. Alternatively, use the command: powershell (Get-Item 'C:\Path\To\IntelMAS.exe').VersionInfo.FileVersionAffected if Unable to retrieve version information from the executable
-
Compare version to 2.5.2Compare the retrieved file version against 2.5.2. Versions prior to 2.5.2 (such as 2.5.1, 2.4.x, or earlier) are considered vulnerable. Versions 2.5.2 and later are patchedAffected if The installed version is lower than 2.5.2 (for example, 2.5.1.x or earlier)
-
Verify default permissions on installation directoryRight-click the Intel installation folder in Program Files\Intel\, select Properties, go to the Security tab, and verify that standard users or low-privileged accounts have elevated write or modify permissions to the application binaries directoryAffected if Non-admin users have write or modify permissions to the application directory, enabling the privilege escalation condition
The system is affected if Intel Memory and Storage Tool is installed with a version lower than 2.5.2 and the application directory has incorrect default permissions allowing low-privileged user modification.
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 · scopedUpdate Intel(R) Memory and Storage Tool to version 2.5.2 or later to remediate the incorrect default permissions vulnerability.
Intel(R) Memory and Storage Tool version 2.5.2 or later
- 1. Download Intel(R) Memory and Storage Tool version 2.5.2 or later from the official Intel support website.
- 2. Close any running instances of Intel Memory and Storage Tool.
- 3. Run the installer with appropriate administrative privileges.
- 4. Follow the installation wizard to complete the update.
- 5. Restart the system if prompted to ensure the new permissions take effect.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36511 — 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-36511 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