CVE-2020-12345
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) Data Center Manager Console before version 3.6.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 confidenceThis is a local privilege escalation vulnerability in the Intel(R) Data Center Manager Console installer. The installer sets improper file or directory permissions that allow an authenticated local user to modify executable files, services, or configurations that run with elevated privileges, enabling privilege escalation.
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< 3.6.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 Intel Data Center Manager installationCheck for Intel Data Center Manager installation directory, typically found in Program Files or Program Files (x86) under Intel or a vendor-named folder. Also check Windows Registry at HKLM\SOFTWARE\Intel\DCM for installation path.Affected if Installation directory exists and version is below 3.6.2
-
Determine installed versionLocate version information in the installation directory (check version.txt, README, or installer log files) or query the Windows Registry under the DCM installation key for the Version value.Affected if Installed version is less than 3.6.2 or version cannot be determined (indicating pre-3.6.2 installation)
-
Inspect installation directory permissionsRight-click the Intel DCM installation folder, go to Properties > Security tab. Examine the permissions for Users or Authenticated Users groups. Alternatively, run: icacls "<installation_path>"Affected if Users or Authenticated Users have Write or Modify permissions on the installation directory or its subfolders containing executables
-
Check for world-writable executables or service binariesRun: icacls "<installation_path>\*" | findstr /i "(F|M|W)" to list files with Full, Modify, or Write access. Focus on .exe, .dll, and service-related configuration files.Affected if Any executable files, DLLs, or service configurations are writable by non-privileged users
Environment is affected if Intel Data Center Manager version is below 3.6.2 AND the installation directory or its executables are writable by standard authenticated users.
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 data3.6.2
Upgrade to Intel Data Center Manager Console version 3.6.2 or later to obtain the patched installer with correct permission settings.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12345 — 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-12345 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