# CVE-2018-17195: Cleartext Transmission of Sensitive Information in Apache nifi

> An attacker can perform CSRF attacks on the template upload API via MiTM, potentially injecting malicious code or modifying data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3jq8-jg75-rqv6

## What is CVE-2018-17195?

CVE-2018-17195 is a high-severity vulnerability in Apache Nifi, published on 19 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The template upload API endpoint accepted requests from different domain when sent in conjunction with ARP spoofing + man in the middle (MiTM) attack, resulting in a CSRF attack. The required attack vector is complex, requiring a scenario with client certificate authentication, same subnet access, and injecting malicious code into an unprotected (plaintext HTTP) website which the targeted user later visits, but the possible damage warranted a Severe severity level. Mitigation: The fix to apply Cross-Origin Resource Sharing (CORS) policy request filtering was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.

Weakness: CWE-863 (Incorrect Authorization), CWE-319 (Cleartext Transmission of Sensitive Information)

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

2 open source packages ship an affected version, including org.apache.nifi:nifi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.nifi:nifi` | Maven | From 1.0.0 | 1.8.0 |
| `org.apache.nifi:nifi` | Maven | From 1.0.0 | 1.8.0 |

Products: Apache Nifi.

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

Upgrade org.apache.nifi:nifi to 1.8.0 or later.

## Is CVE-2018-17195 being exploited?

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

## Other vulnerabilities in Apache Nifi

- [CVE-2018-1309](https://insights.sbomify.com/CVE-2018-1309/): Improper Restriction of XML External Entity Reference in Apache NiFi (critical 9.8)
- [CVE-2017-15697](https://insights.sbomify.com/CVE-2017-15697/): Apache NiFi XSS issue in context path handling (critical 9.8)
- [CVE-2017-5636](https://insights.sbomify.com/CVE-2017-5636/): Injection in Apache NiFi (critical 9.8)
- [CVE-2026-68981](https://insights.sbomify.com/CVE-2026-68981/): Apache NiFi: Uncontrolled Resource Consumption through Decompression of HTTP Requests (high 8.8)
- [CVE-2023-36542](https://insights.sbomify.com/CVE-2023-36542/): Apache NiFi: Potential Code Injection with Properties Referencing Remote Resources (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17195 is a high-severity vulnerability in Apache Nifi, published on 19 Dec 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-17195 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.nifi:nifi (Maven): affected from 1.0.0; fixed in 1.8.0
- org.apache.nifi:nifi (Maven): affected from 1.0.0; fixed in 1.8.0

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-17195/ (Markdown: https://insights.sbomify.com/CVE-2018-17195/index.md)
```

## Sources

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

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