CVE-2019-14605
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 the installer for the Intel(R) SCS Platform Discovery Utility, all versions, may allow an authenticated user to potentially enable escalation of privilege via local attack.
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) SCS Platform Discovery Utility installer contains improper file system permissions that allow an authenticated local user to manipulate installed files or executables in a way that leads to privilege escalation. This is a local, authenticated attack vector requiring the attacker to have valid user credentials on the target system.
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
- High
- Availability
- High
CVSS:3.1/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.
-
Determine if Intel SCS Platform Discovery Utility is installedCheck the system for installed Intel Setup and Configuration Software Platform Discovery Utility. On Windows, review installed programs in Programs and Features, or search for Intel SCS-related executables in typical installation directories such as C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\Affected if The software is present on the system in any version - the vulnerability affects all versions
-
Identify the installation directory and contentsLocate the main installation folder for Intel SCS Platform Discovery Utility. Review all files and subdirectories within it, noting executable files (.exe, .dll) and configuration filesAffected if The software is installed and its directory contains executable files that could be targeted for modification
-
Verify file system permissions on the installation directoryExamine the access control list (ACL) permissions on the Intel SCS installation directory and its contents. Use tools such as icacls (Windows) or examine share and NTFS permissions to determine what users or groups have write or modify accessAffected if Authenticated standard (non-admin) users have write, modify, or full control permissions to the installation directory or its executable files
-
Test whether standard users can modify executablesUsing a standard (non-privileged) user account, attempt to create, modify, or delete files within the Intel SCS installation directory, particularly executable filesAffected if A standard authenticated user can successfully modify, replace, or delete executables in the installation directory
-
Review for unexpected file modificationsCompare the current files in the Intel SCS installation directory against known good baselines or check file timestamps and hashes for any unauthorized modifications to executables or DLLsAffected if Executables or DLLs have been modified by unauthorized users or contain unexpected changes indicating tampering
A user is affected if the Intel SCS Platform Discovery Utility is installed in any version AND standard authenticated users have write or modify access to the installation directory or its executable files, allowing potential privilege escalation through file manipulation.
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 the latest vendor patch or upgrade to a fixed version of the Intel SCS Platform Discovery Utility. If no patch is available, restrict installer/executable access to administrator accounts only and review installed files for unauthorized modifications.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14605 — 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-14605 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