Enterprise Nfv Infrastructure SoftwareApplication · Cisco

CVE-2019-1894

HIGH · 7.2 CVSS v3.0 Published 2019-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, remote attacker with administrator privileges to overwrite or read arbitrary files on the underlying operating system (OS) of an affected device. The vulnerability is due to improper input validation in NFVIS filesystem commands. An attacker could exploit this vulnerability by using crafted variables during the execution of an affected command. A successful exploit could allow the attacker to overwrite or read arbitrary files on the underlying OS.

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 · moderate confidence

This is a command injection vulnerability in Cisco Enterprise NFV Infrastructure Software (NFVIS) where improper input validation in filesystem commands allows an authenticated administrator to read or write arbitrary files on the underlying operating system by using crafted variables.

MitigationApply Cisco's official patch for NFVIS when available, or upgrade to a fixed version. Restrict administrator access to trusted personnel and monitor for unusual filesystem 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
Enterprise Nfv Infrastructure SoftwareApplication
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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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. Confirm NFVIS is installed
    Identify if Cisco Enterprise NFV Infrastructure Software is installed on the system by checking for NFVIS processes, services, or the NFVIS installation directory. Use commands like 'ps aux | grep -i nfvis' or check installed packages.
    Affected if NFVIS is present on the system
  2. Check installed NFVIS version
    Determine the exact version of Cisco NFVIS installed. Compare the installed version to 3.9.1. Use NFVIS CLI commands such as 'show version' or check version files in the NFVIS installation directory.
    Affected if The installed version is exactly 3.9.1
  3. Verify administrator access exists
    Check for administrator accounts or privileged access to NFVIS. Review user accounts configured in NFVIS with administrative privileges using 'show admin' or similar commands.
    Affected if Authenticated administrator accounts exist with access to NFVIS
  4. Inspect for filesystem command anomalies
    Review NFVIS logs and audit records for unusual or crafted filesystem command invocations. Look for patterns indicating arbitrary file read or write operations via the filesystem command interface.
    Affected if Unusual filesystem commands are observed in logs or audit trails

A user is affected if NFVIS version 3.9.1 is running and an authenticated administrator account exists, as the vulnerability requires admin-level access to exploit the improper input validation in filesystem commands.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's official patch for NFVIS when available, or upgrade to a fixed version. Restrict administrator access to trusted personnel and monitor for unusual filesystem command usage.

Fix this in Enterprise Nfv Infrastructure Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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