LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22832: Apache NiFi: Improper Restriction of XML External Entity References in ExtractCCDAAttributes

The 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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Apache NiFi deployments are at risk only when flows use the ExtractCCDAAttributes Processor. A malicious XML document could cause NiFi to resolve external entities and expose sensitive data. The issue is high severity because exploitation is network-reachable, low complexity, and does not require authentication according to the CVSS vector.

Executive priority

Treat this as high priority for any NiFi environment handling XML from outside trusted control. It is less urgent for deployments that do not use ExtractCCDAAttributes, but those should still document non-exposure.

Technical view

CVE-2023-22832 is CWE-611 in Apache NiFi ExtractCCDAAttributes, affecting versions 1.2.0 through 1.19.1. Vulnerable flow configurations process XML documents containing DTDs with XML External Entity references. The documented resolution disables Document Type Definitions and disallows external entity resolution in that processor.

Likely exposure

Exposure is limited to Apache NiFi environments running affected versions and using the ExtractCCDAAttributes Processor in a flow that processes attacker-controlled or untrusted XML documents.

Exploitation context

The bundle does not report CISA KEV listing or active exploitation. CVSS 3.1 rates it 7.5 with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality impact.

Researcher notes

The available sources define affected versions, vulnerable processor conditions, and the intended parser hardening. They do not provide exploit telemetry, a KEV signal, or detailed operational indicators. Validate exposure by configuration, not by product presence alone.

Mitigation direction

  • Identify NiFi instances running versions 1.2.0 through 1.19.1.
  • Upgrade to a NiFi release containing Apache's documented resolution.
  • Confirm vendor guidance for the exact fixed version and deployment steps.
  • Avoid processing untrusted XML through ExtractCCDAAttributes until remediated.
  • Review flows for unexpected XML ingestion paths.

Validation and detection

  • Inventory NiFi versions across production and non-production environments.
  • Search flow configurations for ExtractCCDAAttributes Processor usage.
  • Confirm whether those flows accept untrusted XML documents.
  • Verify the deployed processor blocks DTD and external entity resolution.
  • Check logs for suspicious XML parsing failures or unusual file access indicators.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-611: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-22832 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-22832Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache NiFi1.2.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.