CVE-2020-12287
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 permissions in the Intel(R) Distribution of OpenVINO(TM) Toolkit before version 2020.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 · moderate confidenceLocal privilege escalation vulnerability in Intel Distribution of OpenVINO Toolkit caused by incorrect file system or service permissions that allow an authenticated low-privilege user to gain elevated access via local system interaction.
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< 2020.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.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.
-
Identify installed OpenVINO versionCheck for Intel OpenVINO Toolkit installation. Common installation paths include C:\Program Files (x86)\Intel\openvino_\ or /opt/intel/openvino_/. Look for a version file or check the installation folder name directly.Affected if The installed version is anything before 2020.2 (e.g., 2019.x, 2018.x, or unnamed older versions)
-
Examine OpenVINO installation folder permissionsRight-click the OpenVINO installation directory, go to Properties > Security, and review which users and groups have Full Control, Modify, or Write permissions. On Linux, use 'ls -la' or 'getfacl' to list permissions.Affected if Authenticated standard users (non-admin) have write/modify permissions to system folders or binary directories under the OpenVINO installation path
-
Audit OpenVINO service permissionsOpen Services (services.msc) and look for any Intel OpenVINO-related services. Check the service binary path and review who can stop/start the service and modify its executable.Affected if Low-privilege users can modify service binary paths or restart services that run with elevated privileges
-
Review scripts and executables in OpenVINO foldersExamine .bat, .sh, .exe, and .dll files in the OpenVINO installation for overly permissive access. Check if non-admin users can replace or modify these files.Affected if Standard users have write access to scripts or binaries that execute with elevated privileges
You are affected if the OpenVINO Toolkit version is below 2020.2 AND standard users have excessive permissions to OpenVINO files, folders, or services that could enable privilege escalation.
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 data2020.2
Upgrade to OpenVINO Toolkit version 2020.2 or later; alternatively, audit and remediate file/folder/service permissions to enforce least-privilege access controls.
- Consultation3.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12287 — 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-2020-12287 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