CVE-2019-0109
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 folder permissions in Intel(R) Data Center Manager SDK before version 5.0.2 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 · high confidenceImproper folder permissions in Intel(R) Data Center Manager SDK before version 5.0.2 allow an authenticated local user to modify or replace files in privileged locations, enabling privilege escalation. This is a classic ACL misconfiguration where folders have overly permissive access controls (e.g., write access granted to low-privilege users or Everyone group).
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< 5.0.2CVSS 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 Data Center Manager SDK is installedLook for the SDK installation on the system. Common locations include C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\. Also check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Intel for Data Center Manager entries.Affected if The SDK is present on the system
-
Determine the installed version of Intel Data Center Manager SDKLocate the SDK installation directory and check for version information. This may be in a version file, manifest, or executable properties within the Intel Data Center Manager SDK folder.Affected if The installed version is lower than 5.0.2 (for example, 5.0.1, 5.0.0, or any version < 5.0.2)
-
Examine folder permissions on the SDK installation directoryUse the icacls command or file explorer security tab to inspect ACLs on the main SDK folder and subfolders. Look for access control entries that grant write or modify permissions to non-admin users.Affected if Any folder within the SDK directory grants Write or Modify permissions to Users, Authenticated Users, or the Everyone group
The environment is affected if Intel Data Center Manager SDK version less than 5.0.2 is installed AND the SDK installation folder grants write permissions to standard users or everyone.
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 data5.0.2
Fix folder permissions on the SDK installation directory to follow least-privilege principles—restrict write access to Administrators or SYSTEM only, and upgrade to version 5.0.2 or later.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0109 — 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-0109 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