CVE-2018-1309: Apache NiFi External XML Entity Reference Restriction

Summary

14/05/2022
Yes i
Critical
9.8

CVE-2018-1309: Improper Restriction of XML External Entity Reference in Apache NiFi. Affects org.apache.nifi:nifi-standard-processors versions >= 0.1.0, < 1.6.0. Fixed in 1.6.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache NiFi is an open-source data integration tool that provides a web-based interface for designing, managing, and monitoring data flows. It allows users to collect, transform, and route data between different systems. The SplitXML processor in Apache NiFi is responsible for splitting XML content into separate flow files. However, a vulnerability in this processor allows for improper restriction of XML external entity references, which can lead to information disclosure or remote code execution.

Vulnerability Detail

The vulnerability arises from the lack of proper handling of external general entities and doctype declarations in XML content processed by the SplitXML processor. An attacker can craft malicious XML content that includes external entity references, which can be used to read sensitive files from the server or execute arbitrary code. This can result in unauthorized access to sensitive information, data leakage, or even complete compromise of the affected system. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

How To Fix

Latest published version: 2.12.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.6.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the fixed version of Apache NiFi.

Conclusion

The Apache NiFi SplitXML processor is vulnerable to an external XML entity reference restriction issue, which can lead to information disclosure or remote code execution. Users should upgrade to the fixed version (1.6.0 or later) to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.apache.nifi:nifi-standard-processors →

Share this vulnerability

FAQ

Apache NiFi is an open-source data integration tool that provides a web-based interface for designing, managing, and monitoring data flows.

The SplitXML processor in Apache NiFi is responsible for splitting XML content into separate flow files.

This vulnerability can lead to information disclosure or remote code execution, potentially resulting in unauthorized access to sensitive information, data leakage, or complete compromise of the affected system.

To fix this vulnerability, upgrade to the fixed version of Apache NiFi (1.6.0 or later).

No, there is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the fixed version of Apache NiFi.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.nifi:nifi-standard-processors.

How To Fix

Latest published version: 2.12.0 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.6.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback