dbcve.org
Unified Computing SystemApplication · Cisco

CVE-2019-1725

MEDIUM · 5.5 CVSS v3.1 Published 2019-04-18
Fix available
A fix is available. Upgrade to 4.0 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
A vulnerability in the local management CLI implementation for specific commands on the Cisco UCS B-Series Blade Servers could allow an authenticated, local attacker to overwrite an arbitrary file on disk. It is also possible the attacker could inject CLI command parameters that should not be allowed for a specific subset of local management CLI commands. The vulnerability is due to lack of proper input validation of user input for local management CLI commands. An attacker could exploit this vulnerability by authenticating to the device and issuing a crafted form of a limited subset of local management CLI commands. An exploit could allow the attacker to overwrite an arbitrary files on disk or inject CLI command parameters that should have been disabled. This vulnerability is fixed in software version 4.0(2a) and later.

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

This is a local authenticated vulnerability in Cisco UCS B-Series Blade Servers where the local management CLI lacks proper input validation. An authenticated attacker with CLI access can overwrite arbitrary files on disk or inject CLI command parameters that should be disabled for certain commands.

MitigationUpgrade Cisco UCS B-Series Blade Servers to software version 4.0(2a) or later to remediate this vulnerability.

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
Unified Computing SystemApplication
Affected:< 4.0\(2a\)

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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. Determine Cisco UCS software version
    Access the UCS Manager or UCS Central web interface, or use the 'show version' command via CLI on the UCS B-Series Blade Server. Navigate to Equipment > Equipment Summary > Software Version, or run 'scope sysdebug' then 'show version' in the CLI.
    Affected if The displayed version is earlier than 4.0(2a)
  2. Confirm UCS B-Series Blade Server model
    In UCS Manager, navigate to Equipment > Blade Servers and verify the server model is a B-Series blade (such as B200, B250, B480). Alternatively, use the 'show server identity' CLI command.
    Affected if The hardware is a Cisco UCS B-Series Blade Server (not C-Series rack server or other)
  3. Verify CLI access is enabled
    Check if the local management CLI is accessible via SSH or console connection to the UCS Manager or directly to the blade's CIMC (Cisco Integrated Management Controller). Use the 'show mgmt-if' or check management interface status.
    Affected if CLI access via SSH, console, or CIMC is available (authentication alone is sufficient for exploitation)
  4. Check for local authentication configuration
    Review local user accounts configured in UCS Manager under Admin > User Management > Local Users, or check CIMC local user accounts. Verify that local authentication is enabled.
    Affected if Local user accounts exist and are enabled for CLI access

The environment is affected if the Cisco UCS B-Series Blade Server is running software version earlier than 4.0(2a) and has authenticated CLI access available.

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 4.0 or later
Fixed in 4.0
Interim mitigation

Upgrade Cisco UCS B-Series Blade Servers to software version 4.0(2a) or later to remediate this vulnerability.

Fix this in Unified Computing System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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