dbcve.org
Integrated Management ControllerApplication · Cisco

CVE-2019-1627

MEDIUM · 6.5 CVSS v3.1 Published 2019-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability in the Server Utilities of Cisco Integrated Management Controller (IMC) could allow an authenticated, remote attacker to gain unauthorized access to sensitive user information from the configuration data that is stored on the affected system. The vulnerability is due to insufficient protection of data in the configuration file. An attacker could exploit this vulnerability by downloading the configuration file. An exploit could allow the attacker to use the sensitive information from the file to elevate 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 confidence

Cisco IMC Server Utilities contains a flaw where the configuration file stores sensitive user information without adequate protection. An authenticated attacker can download this configuration file and extract credentials or other sensitive data, which can then be used to escalate privileges on the affected system.

MitigationApply the vendor patch when available. In the interim, restrict access to the Server Utilities functionality to only necessary administrative accounts and monitor for unauthorized configuration file downloads.

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
Integrated Management ControllerApplication
Affected:all versions
Unified Computing SystemApplication
Affected:= 4.0\(1c\)hs3

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 Cisco IMC or UCS installation
    Check system inventory or run 'show version' or 'ipmitool mc info' to identify Cisco Integrated Management Controller or Unified Computing System
    Affected if System is running Cisco IMC (any version) or Cisco UCS version 4.0(1c)hs3
  2. Verify Server Utilities feature status
    Access IMC web interface or CLI and check if Server Utilities functionality is enabled and accessible to administrative accounts
    Affected if Server Utilities feature is enabled and accessible to user accounts
  3. Check configuration file access controls
    Inspect IMC configuration files in the Server Utilities area and verify if sensitive files (user configs, credential stores) are accessible without proper encryption or access restrictions
    Affected if Configuration files containing user credentials are stored without adequate encryption or protection
  4. Review access logs for configuration file downloads
    Search IMC audit logs for unauthorized or unexpected download activity on configuration files, especially those containing user credentials
    Affected if Unusual or unauthorized download activity of configuration files is found in logs
  5. Check for credential exposure in configuration files
    Examine any accessible configuration files for plaintext passwords, hashed credentials, or sensitive user data that could be extracted
    Affected if Configuration files contain unprotected sensitive user information that could be extracted

Your environment is affected if you run Cisco IMC (any version) or Cisco UCS 4.0(1c)hs3 with Server Utilities enabled, and configuration files containing user credentials are accessible or downloadable without proper protection.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available. In the interim, restrict access to the Server Utilities functionality to only necessary administrative accounts and monitor for unauthorized configuration file downloads.

Fix this in Integrated Management Controller Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1627 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1627 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