Data Center ManagerApplication · Intel

CVE-2019-0111

MEDIUM · 5.5 CVSS v3.0 Published 2019-02-18
Fix available
A fix is available. Upgrade to 5.0.2 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper file permissions for Intel(R) Data Center Manager SDK before version 5.0.2 may allow an authenticated user to potentially enable information disclosure 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 confidence

Improper file permissions in Intel(R) Data Center Manager SDK versions before 5.0.2 allow authenticated users to access sensitive information through local file system read access. The vulnerability stems from overly permissive file access controls that fail to restrict confidential data from unauthorized disclosure.

MitigationUpdate Intel Data Center Manager SDK to version 5.0.2 or later. Additionally, review and restrict file permissions on existing installations to follow least-privilege principles.

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
Data Center ManagerApplication
Affected:< 5.0.2

CVSS 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
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Intel Data Center Manager SDK installation
    Locate the Intel Data Center Manager SDK installation directory. Check for presence of DCM SDK components in common installation paths such as C:\Program Files\Intel\DCM or /opt/intel/dcm. Use system inventory tools or check installed programs list.
    Affected if Intel Data Center Manager SDK is installed and the installed version is earlier than 5.0.2
  2. Determine installed version
    Locate the SDK version information, typically found in an about dialog, version file, or manifest within the installation directory. Check files like version.txt, dcm_version, or examine executable metadata.
    Affected if The version returned is less than 5.0.2 or the version cannot be determined
  3. Inspect file permissions on installation directory
    Review file system permissions on the Intel Data Center Manager SDK installation folder. On Windows, right-click the folder, select Properties, then Security tab. On Linux, use 'ls -la' or 'getfacl' commands.
    Affected if Users other than administrators or the owner have Read or Read & Execute permissions to sensitive directories or configuration files within the SDK folder
  4. Check for sensitive files with overly permissive access
    Examine configuration files, log files, and data directories within the SDK installation for world-readable permissions. Look for files containing credentials, credentials, or system information.
    Affected if Non-privileged users can read configuration files, logs, or data files that should be restricted to administrators only

A user is affected if Intel Data Center Manager SDK version 5.0.2 or earlier is installed AND file permissions allow authenticated non-privileged users to read sensitive files within the SDK directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 5.0.2 or later
Fixed in 5.0.2
Interim mitigation

Update Intel Data Center Manager SDK to version 5.0.2 or later. Additionally, review and restrict file permissions on existing installations to follow least-privilege principles.

Fix this in Data Center Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-0111 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-0111 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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