# CVE-2018-15379: Cisco Prime Infrastructure Arbitrary File Upload and Command Execution Vulnerability

> Unauthenticated attackers can upload malicious files via TFTP to execute arbitrary commands on Cisco Prime Infrastructure.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-h92j-m24w-8xp7

## What is CVE-2018-15379?

CVE-2018-15379 is a critical vulnerability in Cisco Prime Infrastructure, published on 5 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in which the HTTP web server for Cisco Prime Infrastructure (PI) has unrestricted directory permissions could allow an unauthenticated, remote attacker to upload an arbitrary file. This file could allow the attacker to execute commands at the privilege level of the user prime. This user does not have administrative or root privileges. The vulnerability is due to an incorrect permission setting for important system directories. An attacker could exploit this vulnerability by uploading a malicious file by using TFTP, which can be accessed via the web-interface GUI. A successful exploit could allow the attacker to run commands on the targeted application without authentication.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-275

## Which versions are affected by CVE-2018-15379?

It affects 1 product.


Products: Cisco Prime Infrastructure.

## How do I fix CVE-2018-15379?

No fix has been published for CVE-2018-15379 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-15379 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15379 exists.

Public exploit code:

- Cisco Prime Infrastructure - (Unauthenticated) Remote Code Execution (exploitdb)
- Cisco Prime Infrastructure Unauthenticated Remote Code Execution (metasploit)

## Other vulnerabilities in Cisco Prime Infrastructure

- [CVE-2014-0679](https://insights.sbomify.com/CVE-2014-0679/): Command injection in n/a (critical 9.0)
- [CVE-2016-1442](https://insights.sbomify.com/CVE-2016-1442/): Command injection in n/a (high 8.8)
- [CVE-2016-1359](https://insights.sbomify.com/CVE-2016-1359/): Code injection in n/a (high 8.8)
- [CVE-2019-1659](https://insights.sbomify.com/CVE-2019-1659/): Cisco Prime Infrastructure Certificate Validation Vulnerability (high 7.4)
- [CVE-2015-6262](https://insights.sbomify.com/CVE-2015-6262/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15379 and fix it if it is affected.

What it is: CVE-2018-15379 is a critical vulnerability in Cisco Prime Infrastructure, published on 5 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-15379 exists.

Affected product: Cisco Prime Infrastructure. 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-15379/ (Markdown: https://insights.sbomify.com/CVE-2018-15379/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-15379
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-15379
- OSV: https://osv.dev/vulnerability/CVE-2018-15379

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-15379/
Summaries are generated and may contain mistakes; the official description above is the record.