Network Functions Virtualization InfrastructureApplication · Cisco

CVE-2018-0324

MEDIUM · 6.7 CVSS v3.1 Published 2018-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 CLI of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, high-privileged, local attacker to perform a command injection attack. The vulnerability is due to insufficient input validation of command parameters in the CLI parser. An attacker could exploit this vulnerability by invoking a vulnerable CLI command with crafted malicious parameters. An exploit could allow the attacker to execute arbitrary commands with a non-root user account on the underlying Linux operating system of the affected device. Cisco Bug IDs: CSCvi09723.

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 command injection vulnerability exists in the CLI parser of Cisco Enterprise NFV Infrastructure Software (NFVIS) due to insufficient input validation of command parameters. An authenticated high-privileged local attacker can exploit this by invoking vulnerable CLI commands with crafted malicious parameters, allowing execution of arbitrary commands on the underlying Linux OS with non-root user privileges.

MitigationApply the Cisco vendor patch for CSCvi09723 to remediate the input validation flaw in the CLI parser. Until the patch is available, restrict CLI access to only absolutely necessary high-privileged users and monitor for suspicious command activity.

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
Network Functions Virtualization InfrastructureApplication
Affected:= 3.6.1= 3.6.2= 3.7.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco NFVIS is installed
    Run 'show version' in the CLI or check system boot logs to verify the system is running Cisco Enterprise NFV Infrastructure Software
    Affected if System is running Cisco NFVIS
  2. Check NFVIS version number
    Execute 'show version' command in the CLI or inspect system information to obtain the exact NFVIS version
    Affected if Version equals 3.6.1, 3.6.2, or 3.7.1 exactly
  3. Verify CLI interface is accessible
    Attempt to access the NFVIS CLI or check network configuration to confirm CLI management interface is enabled and reachable
    Affected if CLI interface is accessible to authenticated users
  4. Identify authenticated high-privileged users
    Review local user accounts and their privilege levels using 'show user' or similar administrative commands
    Affected if High-privileged local user accounts exist with CLI access

Environment is affected if running Cisco NFVIS version 3.6.1, 3.6.2, or 3.7.1 with CLI accessible to authenticated high-privileged users.

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 the Cisco vendor patch for CSCvi09723 to remediate the input validation flaw in the CLI parser. Until the patch is available, restrict CLI access to only absolutely necessary high-privileged users and monitor for suspicious command activity.

Fix this in Network Functions Virtualization Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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