CVE-2019-0121
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 permissions in Intel(R) Matrix Storage Manager 8.9.0.1023 and before 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 Matrix Storage Manager versions 8.9.0.1023 and earlier contain improper permission configurations that allow an authenticated local user to escalate privileges, potentially gaining elevated system access.
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<= 8.9.0.1023CVSS 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.0/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.
-
Check if Intel Matrix Storage Manager is installedOpen Programs and Features (appwiz.cpl) or check for Intel Matrix Storage Manager in the list of installed programs. Alternatively, search for installation directories under C:\Program Files\Intel or C:\Program Files (x86)\Intel containing 'Matrix Storage' or 'ISM' in the folder name.Affected if The software is listed as installed or Intel storage-related directories exist on the system
-
Determine installed version of Intel Matrix Storage ManagerRight-click the installed program in Programs and Features and select Properties, then view the Version field. Or locate the main executable (typically iaStor.sys, iaStorA.sys, or similar in the installation folder) and check its file properties for version information.Affected if The displayed version is 8.9.0.1023 or any version number lower than this (for example, 8.9.0.1022, 8.8.x.x, etc.)
-
Verify the software components are present and accessibleNavigate to the Intel Matrix Storage Manager installation directory (commonly C:\Program Files\Intel\Intel(R) Matrix Storage Manager or similar path) and confirm the driver files and service executables exist. Check file permissions on these files to see if standard users can modify them.Affected if The installation directory and core component files exist and are accessible to authenticated local users without administrative privileges
A system is affected if Intel Matrix Storage Manager version 8.9.0.1023 or earlier is installed and the component files are present on the system.
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 dataUpgrade to a patched version of Intel Matrix Storage Manager beyond 8.9.0.1023, or implement restrictive file/system permissions on the affected software components if no update is available.
- 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-2019-0121 — 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-2019-0121 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