dbcve.org
Firepower Extensible Operating SystemOperating system · Cisco

CVE-2019-1734

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-05
Fix available
A fix is available. Upgrade to 2.2.2.91 / 2.3.1.111 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 implementation of a CLI diagnostic command in Cisco FXOS Software and Cisco NX-OS Software could allow an authenticated, local attacker to view sensitive system files that should be restricted. The attacker could use this information to conduct additional reconnaissance attacks. The vulnerability is due to incomplete role-based access control (RBAC) verification. An attacker could exploit this vulnerability by authenticating to the device and issuing a specific CLI diagnostic command with crafted user-input parameters. An exploit could allow the attacker to perform an arbitrary read of a file on the device, and the file may contain sensitive information. The attacker needs valid device credentials to exploit this vulnerability.

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 an authenticated local file read vulnerability in Cisco FXOS and NX-OS software. The issue stems from incomplete role-based access control (RBAC) validation in a specific CLI diagnostic command, allowing an authenticated attacker with valid credentials to read arbitrary files on the device by supplying crafted user-input parameters.

MitigationApply the Cisco software update (patch) when available from Cisco. In the interim, limit access to device credentials and monitor for suspicious CLI diagnostic command usage.

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
Firepower Extensible Operating SystemOperating system
Affected:< 2.2.2.91>= 2.3, < 2.3.1.111>= 2.4, < 2.4.1.101
Nx OsOperating system
Affected:< 6.2\(7\)< 7.0\(3\)i4\(9\)>= 7.0\(3\)i7, < 7.0\(3\)i7\(6\)< 6.0\(2\)a4\(1\)>= 7.0\(3\)i4, < 7.0\(3\)i4\(9\)>= 7.0\(3\), < 7.0\(3\)f3\(5\)< 7.1\(4\)n1\(1\)>= 7.2, < 7.3\(0\)n1\(1\)< 6.2\(6\)< 4.0\(1a\)

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.1/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 the installed product and version
    Run 'show version' or 'show inventory' on the device CLI to obtain the exact software version
    Affected if The version falls within any of the listed affected ranges for FXOS or NX-OS
  2. Confirm the device runs FXOS or NX-OS
    Verify the operating system type from the 'show version' output - look for 'Cisco FXOS' or 'Cisco NX-OS' in the OS description
    Affected if The device runs FXOS or NX-OS and the version is vulnerable
  3. Check for the vulnerable CLI diagnostic command
    Attempt to access or document the specific diagnostic command that lacks proper RBAC validation - consult Cisco advisory for the exact command name
    Affected if The diagnostic command exists and is accessible to authenticated users
  4. Review user role assignments
    Use 'show role' or 'show user-account' to list assigned roles for users with CLI access
    Affected if Users with non-admin roles can access the vulnerable diagnostic command
  5. Audit recent CLI command history
    Review logs or use 'show logging' to look for suspicious use of diagnostic file-read commands
    Affected if Unusual or unauthorized diagnostic file-read commands were executed

The environment is affected if the device runs a vulnerable FXOS or NX-OS version AND an authenticated user can access the CLI diagnostic command with insufficient RBAC controls.

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 2.2.2.91 / 2.3.1.111 / 2.4.1.101 or later
Fixed in 2.2.2.912.3.1.1112.4.1.101
Interim mitigation

Apply the Cisco software update (patch) when available from Cisco. In the interim, limit access to device credentials and monitor for suspicious CLI diagnostic command usage.

Fix this in Firepower Extensible Operating System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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