# CVE-2018-11652: Command injection in n/a

> Remote attackers can execute arbitrary OS commands by injecting malicious data into the Server header of HTTP responses processed by Nikto.

- **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:** Yes
- **Published:** 1 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-11652, DEBIAN-CVE-2018-11652, GHSA-pmf5-gx6h-8x53, MGASA-2018-0310, UBUNTU-CVE-2018-11652

## What is CVE-2018-11652?

CVE-2018-11652 is a critical command injection vulnerability in n/a, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CSV Injection vulnerability in Nikto 2.1.6 and earlier allows remote attackers to inject arbitrary OS commands via the Server field in an HTTP response header, which is directly injected into a CSV report.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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

It affects 1 product.


Products: Cirt.net Nikto.

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

Upgrade to a fixed version.

## Is CVE-2018-11652 being exploited?

There is no known exploitation of CVE-2018-11652 in the wild and no public exploit code.

Public exploit code:

- Nikto 2.1.6 - CSV Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11652 is a critical command injection vulnerability in n/a, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11652 in the wild and no public exploit code.

Affected product: n/a. 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-11652/ (Markdown: https://insights.sbomify.com/CVE-2018-11652/index.md)
```

## Sources

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

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