NifiApplication · Apache
CVE-2023-22832
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 ExtractCCDAAttributes Processor in Apache NiFi 1.2.0 through 1.19.1 does not restrict XML External Entity references. Flow configurations that include the ExtractCCDAAttributes Processor are vulnerable to malicious XML documents that contain Document Type Declarations with XML External Entity references. The resolution disables Document Type Declarations and disallows XML External Entity resolution in the ExtractCCDAAttributes Processor.
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 ExtractCCDAAttributes Processor in Apache NiFi 1.2.0 through 1.19.1 does not restrict XML External Entity (XXE) references, allowing malicious XML documents with crafted Document Type Declarations (DTDs) to reference external entities and potentially exfiltrate sensitive data or perform server-side request forgery.
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.2.0, <= 1.19.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check the installed Apache NiFi versionLocate the NiFi installation directory and check the release file or run 'nifi.sh version' if available. Common locations include /opt/nifi or the installation root directory.Affected if The installed version is >= 1.2.0 and <= 1.19.1
-
Identify if the ExtractCCDAAttributes Processor exists in any flowReview NiFi canvas for processors named 'ExtractCCDAAttributes' or search in the NiFi repository XML files (flow.json or the flow XML export) for this processor type.Affected if The processor is present in any active or saved data flow configuration
-
Determine if the processor is actively runningIn the NiFi web UI, locate the ExtractCCDAAttributes Processor and check its status. Alternatively, inspect the flow configuration to see if the processor is enabled.Affected if The processor is in a 'Running' state and scheduled to execute
-
Assess the source of XML data being processedInspect the incoming connections to the ExtractCCDAAttributes Processor to determine if the XML data originates from untrusted or external sources.Affected if The processor processes XML from untrusted or external sources
You are affected if NiFi version is between 1.2.0 and 1.19.1 AND the ExtractCCDAAttributes Processor is actively running and processing untrusted XML documents.
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.
dbcve · scopedUpgrade Apache NiFi to version 1.20.0 or later, which disables Document Type Declarations and disallows XML External Entity resolution in the ExtractCCDAAttributes Processor. Alternatively, avoid processing untrusted XML with the ExtractCCDAAttributes Processor until upgrade is possible.
Nifi 1.20.0 or later
- Upgrade Apache NiFi to version 1.20.0 or later to include the security fix that disables Document Type Declarations and XML External Entity resolution in the ExtractCCDAAttributes Processor
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nifi
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22832 — 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-2023-22832 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