Enterprise Network Function Virtualization Infrastructure SofwareApplication · Cisco
CVE-2019-1984
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 · uneditedA vulnerability in Cisco Enterprise Network Functions Virtualization Infrastructure Software (NFVIS) could allow an authenticated, remote attacker with administrator privileges to overwrite files on the underlying operating system (OS) of an affected device. The vulnerability is due to improper input validation in an NFVIS file-system command. 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 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 · high confidenceThis is an improper input validation vulnerability in Cisco NFVIS file-system commands that allows authenticated administrators to overwrite arbitrary files on the underlying operating system. The attacker exploits the vulnerability by using crafted variables in an affected file-system command, achieving OS-level file write access beyond the application sandbox.
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 Infrastructure SofwareApplication
< 3.12.1CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NFVIS versionLog into the Cisco NFVIS CLI and run the command to display the software version, typically 'show version' or 'show system information'. Look for the software version number in the output.Affected if The displayed version number is lower than 3.12.1 (for example, 3.12.0, 3.11.x, or earlier).
-
Confirm file-system command accessVerify that administrator-level CLI access is available. In NFVIS, file-system commands are typically accessed through the ' Exec' mode or specific file operation commands. Check if you can access commands related to file operations such as file copy, file move, or file upload functionalities.Affected if Authenticated administrators can access and execute file-system commands in the NFVIS CLI.
-
Review administrator accountsList all configured administrator accounts and their privilege levels using commands like 'show running-config' or 'show admin' to see which users have administrative privileges.Affected if There are multiple administrator accounts or the account privilege levels cannot be verified as trusted.
-
Audit recent file-system command usageReview system logs, audit logs, or command history for any executed file-system commands. Look for commands that involve file operations, particularly those using variables or parameters that could indicate attempts to write outside the application sandbox.Affected if There are logged file-system commands that use crafted variables or unusual file paths pointing to system directories outside the NFVIS sandbox.
Your environment is affected if the installed Cisco NFVIS version is lower than 3.12.1 and administrators have access to file-system commands that could be exploited with crafted variables to write files outside the application sandbox.
Generated from the published advisory. Verify against your own configuration.
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 data3.12.1
Apply the Cisco patch for CVE-2019-1984 when available. Until then, limit administrator access to trusted personnel only and monitor for suspicious file-system command usage.
Fix this in Enterprise Network Function Virtualization Infrastructure Sofware
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1984 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1984 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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