Enterprise Network Function Virtualization InfrastructureApplication · Cisco

CVE-2020-3138

MEDIUM · 6.7 CVSS v3.1 Published 2020-02-19
Fix available
A fix is available. Upgrade to after 3.11.1 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 upgrade component of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, local attacker to install a malicious file when upgrading. The vulnerability is due to insufficient signature validation. An attacker could exploit this vulnerability by providing a crafted upgrade file. A successful exploit could allow the attacker to upload crafted code to the 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 exists in the upgrade component of Cisco Enterprise NFV Infrastructure Software (NFVIS) where insufficient signature validation allows an authenticated, local attacker to install malicious files during the upgrade process. By providing a crafted upgrade file, the attacker can upload arbitrary code to the affected device, achieving code execution with the privileges of the upgrade component.

MitigationApply the vendor patch from Cisco when available, and ensure local authentication mechanisms are properly secured to limit exposure to authenticated local attackers.

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
Enterprise Network Function Virtualization InfrastructureApplication
Affected:<= 3.11.1

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. Determine NFVIS installed version
    Run 'show version' or access the NFVIS admin CLI and check the software version displayed
    Affected if The displayed version is 3.11.1 or lower (any version <= 3.11.1)
  2. Confirm local authentication is enabled
    Check if local user accounts exist on the system via 'show running-config | include username' or review authentication settings in the admin UI under Users/AAA
    Affected if Local authentication is configured and accessible, providing an attacker a path to obtain valid credentials
  3. Verify upgrade functionality is accessible
    Review the upgrade menu in NFVIS admin UI or check for 'upgrade' commands in the CLI; confirm the upgrade feature is not explicitly disabled
    Affected if The upgrade component is present and enabled on the system (this is the vulnerable component)
  4. Review recent upgrade activity logs
    Access upgrade logs via 'show upgrade log' or check /var/log/upgrade* files for any recent upgrade operations
    Affected if There are recent upgrade attempts from unexpected sources or at unusual times, or logs show signature validation failures that were overridden

A system is affected if it runs Cisco NFVIS version 3.11.1 or lower AND has the upgrade component accessible with local authentication enabled.

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 a release after 3.11.1
Interim mitigation

Apply the vendor patch from Cisco when available, and ensure local authentication mechanisms are properly secured to limit exposure to authenticated local attackers.

Fix this in Enterprise Network Function Virtualization Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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