dbcve.org
Enterprise Network Function Virtualization InfrastructureApplication · Cisco

CVE-2019-1895

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-07
Fix available
A fix is available. Upgrade to 3.12.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Virtual Network Computing (VNC) console implementation of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an unauthenticated, remote attacker to access the VNC console session of an administrative user on an affected device. The vulnerability is due to an insufficient authentication mechanism used to establish a VNC session. An attacker could exploit this vulnerability by intercepting an administrator VNC session request prior to login. A successful exploit could allow the attacker to watch the administrator console session or interact with it, allowing admin access 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

A vulnerability in Cisco NFVIS VNC console allows unauthenticated remote attackers to intercept or hijack administrator VNC sessions due to insufficient authentication during session establishment. An attacker can watch or interact with the admin console, gaining full admin access to the affected NFV Infrastructure Software device.

MitigationApply the Cisco patch for CVE-2019-1895 when available. As a compensating control, restrict network access to VNC ports (typically 5900+) via firewall rules or ACLs, and consider disabling VNC if not operationally critical until the patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if Cisco NFVIS is installed
    Check system for NFVIS installation or running processes. Look for NFVIS-specific processes, directories, or the presence of NFVIS administrative interfaces.
    Affected if NFVIS software is not present on the system
  2. Determine the installed NFVIS version
    Access the NFVIS CLI or administrative interface and run the command to display the version, such as 'show version' or 'show system information'. Compare the displayed version against the affected range of versions prior to 3.12.1.
    Affected if The installed version is lower than 3.12.1
  3. Verify if VNC feature is enabled
    Check the NFVIS configuration for VNC server settings. Look for VNC-related configuration commands or the presence of VNC server processes listening on ports 5900 and above.
    Affected if VNC functionality is enabled and the system is listening on VNC ports
  4. Check network exposure of VNC ports
    Scan the network interface or review firewall rules to determine if VNC ports (typically 5900+) are exposed to untrusted networks. Use 'netstat' or 'ss' to list listening ports, and review any accessible VNC endpoints.
    Affected if VNC ports are accessible from untrusted network segments

A system is affected if it runs Cisco NFVIS with a version below 3.12.1, has the VNC feature enabled, and has VNC ports (5900+) exposed to network attackers.

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.

dbcve · scoped
Upgrade available Upgrade to 3.12.1 or later
Fixed in 3.12.1
Interim mitigation

Apply the Cisco patch for CVE-2019-1895 when available. As a compensating control, restrict network access to VNC ports (typically 5900+) via firewall rules or ACLs, and consider disabling VNC if not operationally critical until the patch is applied.

Recommended fix High confidence

Cisco Enterprise NFV Infrastructure Software 3.12.1 or later

  1. Backup the current NFVIS configuration and export any critical data
  2. Access the NFVIS admin console or CLI
  3. Navigate to the software upgrade section
  4. Obtain Cisco NFVIS version 3.12.1 or later from Cisco (via tools.cisco.com or official Cisco support channels)
  5. Upload the upgrade image to the NFVIS device
  6. Initiate the upgrade process and monitor for completion
  7. After reboot, verify the running version is 3.12.1 or later using 'show version' command
  8. Verify the VNC console now properly requires authentication before session establishment
Caveat Review Cisco NFVIS 3.12.1 release notes for any feature changes or migration considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Network Function Virtualization Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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