CVE-2017-5682
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 · uneditedIntel PSET Application Install wrapper of Intel Parallel Studio XE, Intel System Studio, Intel VTune Amplifier, Intel Inspector, Intel Advisor, Intel MPI Library, Intel Trace Analyzer and Collector, Intel Integrated Performance Primitives, Cryptography for Intel Integrated Performance Primitives, Intel Math Kernel Library, Intel Data Analytics Acceleration Library, and Intel Threading Building Blocks before 2017 Update 2 allows an attacker to launch a process with escalated privileges.
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 confidenceLocal privilege escalation vulnerability in Intel PSET Application Install wrapper affecting multiple Intel development tools. The install wrapper improperly handles privilege escalation, allowing a local attacker to launch processes with elevated privileges beyond the intended installation context.
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= 2017= 2017= 2017= 2017= 2017= 2017= 2017= 2017CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/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.
-
List installed Intel development toolsOpen Windows Control Panel > Programs and Features or use 'wmic product get name,version' to enumerate installed Intel software. Look specifically for Intel Advisor, Intel Inspector, Intel Parallel Studio Xe, Intel MPI Library, Intel MKL, Intel IPP, Intel DAAL, or Intel Cryptography for IPP installed in 2017.Affected if Any of the listed Intel 2017 products (Advisor, Inspector, Parallel Studio Xe, MPI Library, MKL, IPP, DAAL, or Cryptography for IPP) appear in the installed programs list.
-
Locate the PSET Application Install wrapperSearch for files named 'pset.exe', 'pset.dll', or folders named 'pset' within the Intel installation directories. Common paths include C:\Program Files\Intel\ or C:\Program Files (x86)\Intel\. The PSET wrapper is typically found in the installer or setup subdirectories of Intel tool installations.Affected if The PSET (Privilege Set) Application Install wrapper component is present on the system.
-
Determine PSET wrapper versionRight-click the pset.exe or pset.dll file, select Properties, then view the Details tab to check the File Version and Product Version. Alternatively, use 'powershell (Get-Item "C:\path\to\pset.exe").VersionInfo' to retrieve version information.Affected if The PSET wrapper version is 2017 (any sub-version) but NOT Update 2 or later. Versions prior to the 2017 Update 2 patch are vulnerable.
-
Check PSET wrapper file permissionsRight-click the PSET wrapper executable folder, select Properties > Security tab. Review the permissions for Users, Everyone, or non-admin groups. Verify if unprivileged local users have Write, Modify, or Write+Execute permissions to the PSET components.Affected if Non-administrator users have write or execute permissions on the PSET install wrapper files, allowing them to inject or modify the wrapper to escalate privileges.
A system is affected if any Intel 2017 development tool is installed AND the PSET Application Install wrapper component exists with a version prior to 2017 Update 2 AND unprivileged users can modify the PSET files.
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 all affected Intel products (Parallel Studio XE, System Studio, VTune Amplifier, Inspector, Advisor, MPI Library, Trace Analyzer, IPP, MKL, DAAL, TBB) to 2017 Update 2 or later which contains the patched PSET wrapper.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5682 — 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-2017-5682 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