Enterprise Network Function Virtualization InfrastructureApplication · Cisco
CVE-2019-1952
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 the CLI of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, local attacker to overwrite or read arbitrary files. The attacker would need valid administrator privilege-level credentials. This vulnerability is due to improper input validation of CLI command arguments. An attacker could exploit this vulnerability by using directory traversal techniques when executing a vulnerable command. A successful exploit could allow the attacker to overwrite or read arbitrary files on an 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 · moderate confidenceThe vulnerability exists in the CLI of Cisco Enterprise NFV Infrastructure Software where CLI command arguments lack proper input validation. An authenticated administrator can exploit this by using directory traversal techniques (e.g., ../../) within vulnerable CLI commands to read or overwrite arbitrary files on the underlying filesystem with the privileges of the NFVIS administrator account.
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
< 3.10.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed NFVIS versionAccess the CLI via console or SSH and run the command 'show version' or check via the management interface. Locate the software version string in the output.Affected if The displayed version number is lower than 3.10.1 (for example, 3.9.x, 3.8.x, or earlier releases).
-
Confirm CLI access is enabledVerify that the NFVIS CLI is accessible via console, SSH, or remote management. Check whether network services listening on CLI ports (typically port 22 for SSH) are active.Affected if CLI access is available and the system is running an affected version.
-
Review administrator account accessUse the command 'show admin-user' or list current administrator accounts configured in NFVIS to identify who has CLI access privileges.Affected if Any administrator account exists on the system running an affected version, since the vulnerability can be exploited by any authenticated administrator.
-
Inspect for recent suspicious CLI activityReview system logs or audit logs for CLI commands containing directory traversal patterns such as '../', '../', or unusual file path references in command arguments.Affected if Log entries show CLI commands with traversal sequences executed on an affected version, indicating active exploitation attempts.
The environment is affected if Cisco Enterprise NFV Infrastructure Software is running any version lower than 3.10.1 and the CLI is accessible to authenticated administrators.
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.10.1
Apply the vendor patch from Cisco for this vulnerability. Until patched, strictly limit CLI access to trusted administrators only and monitor for suspicious directory traversal patterns in CLI commands.
Fix this in Enterprise Network Function Virtualization Infrastructure
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1952 — 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-1952 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