NifiApplication · Apache
CVE-2019-10080
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI instance uses.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe XMLFileLookupService in Apache NiFi versions 1.3.0 to 1.9.2 is vulnerable to XML External Entity (XXE) injection. This allows trusted users to configure malicious XML files that can make external calls and exfiltrate sensitive system information including Java, Jersey, and Apache version details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
NifiApplication
>= 1.3.0, <= 1.9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify NiFi installation versionLocate the NiFi installation and check the version identifier, typically found in the NiFi release file, nifi.properties file, or the lib directory containing nifi-core jars. Common locations include $NIFI_HOME/RELEASE or the JAR manifest attributes.Affected if The installed version falls within the range 1.3.0 to 1.9.2 inclusive.
-
Confirm XMLFileLookupService is in useReview NiFi flow configurations (such as flow.xml.gz) or lookup service definitions to determine if XMLFileLookupService has been configured as a lookup service in any processor or controller service.Affected if XMLFileLookupService is configured and actively used within the NiFi flow.
-
Check XML parser configuration for external entity settingsExamine the XML parser configuration used by the XMLFileLookupService. Look for settings related to external entity processing, DOCTYPE declarations, or XXE protection. This may be in parser-specific configuration files or programmatically set within the service.Affected if External entity processing is enabled or no XXE protection is explicitly configured in the XML parser.
A user is affected if they are running NiFi version 1.3.0 through 1.9.2 and have XMLFileLookupService configured with external entity processing enabled in the XML parser.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade NiFi to version 1.10.0 or later which contains the patch, or implement XXE protection by disabling external entity processing in the XML parser used by XMLFileLookupService.
Fix this in Nifi
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10080 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data