# CVE-2018-0279: Command injection in Cisco Enterprise NFV Infrastructure Software > Authenticated attackers can inject commands via SCP to gain Linux shell access on Cisco NFVIS devices, potentially leading to further system compromise. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 17 May 2018 - **Updated:** 29 Nov 2024 - **Also known as:** GHSA-2534-25mr-h93h ## What is CVE-2018-0279? CVE-2018-0279 is a high-severity command injection vulnerability in Cisco Enterprise NFV Infrastructure Software, published on 17 May 2018. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A vulnerability in the Secure Copy Protocol (SCP) server of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an authenticated, remote attacker to access the shell of the underlying Linux operating system on the affected device. The vulnerability is due to improper input validation of command arguments. An attacker could exploit this vulnerability by using crafted arguments when opening a connection to the affected device. An exploit could allow the attacker to gain shell access with a non-root user account to the underlying Linux operating system on the affected device. Due to the system design, access to the Linux shell could allow execution of additional attacks that may have a significant impact on the affected system. This vulnerability affects Cisco devices that are running release 3.7.1, 3.6.3, or earlier releases of Cisco Enterprise NFV Infrastructure Software (NFVIS) when access to the SCP server is allowed on the affected device. Cisco NFVIS Releases 3.5.x and 3.6.x do allow access to the SCP server by default, while Cisco NFVIS Release 3.7.1 does not. Cisco Bug IDs: CSCvh25026. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2018-0279? It affects 1 product. Products: Cisco Enterprise Nfv Infrastructure Software. ## How do I fix CVE-2018-0279? No fix has been published for CVE-2018-0279 yet. Limit exposure of the affected software until one is available. ## Is CVE-2018-0279 being exploited? There is no known exploitation of CVE-2018-0279 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Enterprise NFV Infrastructure Software - [CVE-2022-20777](https://insights.sbomify.com/CVE-2022-20777/): Cisco Enterprise NFV Infrastructure Software Vulnerabilities (critical 9.9) - [CVE-2022-20779](https://insights.sbomify.com/CVE-2022-20779/): Cisco Enterprise NFV Infrastructure Software Vulnerabilities (critical 9.9) - [CVE-2022-20780](https://insights.sbomify.com/CVE-2022-20780/): Cisco Enterprise NFV Infrastructure Software Vulnerabilities (critical 9.9) - [CVE-2021-34746](https://insights.sbomify.com/CVE-2021-34746/): Cisco Enterprise NFV Infrastructure Software Authentication Bypass Vulnerability (critical 9.8) - [CVE-2020-3470](https://insights.sbomify.com/CVE-2020-3470/): Cisco Integrated Management Controller Multiple Remote Code Execution Vulnerabilities (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-0279 and fix it if it is affected. What it is: CVE-2018-0279 is a high-severity command injection vulnerability in Cisco Enterprise NFV Infrastructure Software, published on 17 May 2018. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-0279 in the wild and no public exploit code. Affected product: Cisco Enterprise NFV Infrastructure Software. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-0279/ (Markdown: https://insights.sbomify.com/CVE-2018-0279/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-0279 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-0279 - OSV: https://osv.dev/vulnerability/CVE-2018-0279 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-0279/ Summaries are generated and may contain mistakes; the official description above is the record.