Enterprise Network Function Virtualization InfrastructureApplication · Cisco

CVE-2019-1953

MEDIUM · 6.5 CVSS v3.1 Published 2019-08-08
Fix available
A fix is available. Upgrade to 3.9.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 web portal of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, remote attacker to view a password in clear text. The vulnerability is due to incorrectly logging the admin password when a user is forced to modify the default password when logging in to the web portal for the first time. Subsequent password changes are not logged and other accounts are not affected. An attacker could exploit this vulnerability by viewing the admin clear text password and using it to access the affected system. The attacker would need a valid user account 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

In Cisco NFV Infrastructure Software, the web portal incorrectly logs the admin user's password in clear text when a forced password change occurs during first login. This occurs because the password change process writes the new plaintext password to system logs rather than handling it properly. An attacker with a valid user account can view these logs to recover the admin's plaintext password.

MitigationReview system logs for any instances of plaintext admin passwords and clear or redact them. Change the admin password immediately if not already done since first login. Apply vendor patch when available to fix the logging mechanism.

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

CVSS:3.1/AV:N/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 installed version
    Run 'show version' or check the NFVIS management interface for the current software version number
    Affected if The installed version is lower than 3.9.1 (for example, 3.8.x, 3.7.x, etc.)
  2. Determine if web portal is enabled
    Access the NFVIS CLI or web interface and check the web portal service status (typically via 'show webui status' or through the management GUI settings)
    Affected if The web portal/management interface is enabled and accessible
  3. Examine system logs for plaintext passwords
    Review system logs (via 'show log' command, /var/log directory, or the web portal audit logs) for any entries containing 'password' or the admin username that show plaintext credential strings
    Affected if Log entries contain plaintext password strings for the admin account (particularly during first-time login scenarios)

You are affected if your NFVIS version is below 3.9.1, the web portal is enabled, and plaintext admin passwords appear in system logs from first login password changes.

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

Review system logs for any instances of plaintext admin passwords and clear or redact them. Change the admin password immediately if not already done since first login. Apply vendor patch when available to fix the logging mechanism.

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-1953 — 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-2019-1953 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