dbcve.org
Nx OsOperating system · Cisco

CVE-2019-1813

MEDIUM · 6.7 CVSS v3.1 Published 2019-05-15
Fix available
A fix is available. Upgrade to 7.0 / 9.2 or later.
See remediation →
69/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 Image Signature Verification feature of Cisco NX-OS Software could allow an authenticated, local attacker with administrator-level credentials to install a malicious software image on an affected device. The vulnerability exists because software digital signatures are not properly verified during CLI command execution. An attacker could exploit this vulnerability to install an unsigned software image on an affected device.

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

The vulnerability allows an authenticated administrator to bypass image signature verification in Cisco NX-OS, enabling installation of unsigned malicious software images. The root cause is improper digital signature validation during CLI command execution for software image installation.

MitigationApply the Cisco-provided patch for affected NX-OS versions. Only allow trusted administrators access to the device and verify all software images before installation.

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
Nx OsOperating system
Affected:>= 7.0\(3\)i1\(x\), < 7.0\(3\)i7\(5\)>= 9.2, < 9.2\(2\)>= 7.0\(3\), < 7.0\(3\)f3\(5\)< 7.0\(3\)i7\(5\)

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

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

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

  1. Check installed NX-OS version
    Run 'show version' on the NX-OS device CLI and note the installed software version
    Affected if The version falls within these ranges: 7.0(3)i1(x) through 7.0(3)i7(4), 9.2 through 9.2(1), 7.0(3) through 7.0(3)f3(4), or any version before 7.0(3)i7(5) that is not otherwise listed in the fixed releases
  2. Verify image signature verification configuration
    Run 'show running-config | include signature' or 'show software authenticity' commands to examine whether digital signature verification is enabled for software images
    Affected if Signature verification is disabled, not properly enforced, or the configuration shows default-allow behavior for image installation
  3. Review recent image installation command logs
    Run 'show logging logfile | include install' or 'show command-history' to inspect recent software installation commands executed on the device
    Affected if Any image installation or upgrade commands were run by an authenticated administrator, as the vulnerability allows bypassing signature validation during these operations
  4. Check administrator access and command authorization
    Run 'show users' and 'show privilege' to identify current authenticated administrators, then review 'show role' or 'show user-account' for permission levels
    Affected if Any authenticated administrator account exists, as the vulnerability can be exploited by any admin-level user to bypass signature verification

The environment is affected if the NX-OS version matches the affected ranges AND the device allows authenticated administrator access to perform software image installation operations.

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 7.0 / 9.2 or later
Fixed in 7.09.2
Interim mitigation

Apply the Cisco-provided patch for affected NX-OS versions. Only allow trusted administrators access to the device and verify all software images before installation.

Fix this in Nx Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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