dbcve.org
NifiApplication · Apache

CVE-2023-34212

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to after 1.21.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The JndiJmsConnectionFactoryProvider Controller Service, along with the ConsumeJMS and PublishJMS Processors, in Apache NiFi 1.8.0 through 1.21.0 allow an authenticated and authorized user to configure URL and library properties that enable deserialization of untrusted data from a remote location. The resolution validates the JNDI URL and restricts locations to a set of allowed schemes. You are recommended to upgrade to version 1.22.0 or later which fixes this issue.

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 confidence

Apache NiFi versions 1.8.0-1.21.0 contain a JNDI injection vulnerability in the JndiJmsConnectionFactoryProvider Controller Service and ConsumeJMS/PublishJMS Processors. Authenticated users with authorization to configure these components can specify malicious JNDI URLs and library properties that enable deserialization of untrusted data from remote locations, potentially leading to remote code execution.

MitigationUpgrade to Apache NiFi 1.22.0 or later, which implements validation of JNDI URLs and restricts them to an allowed set of schemes.

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
Affected:>= 1.8.0, <= 1.21.0

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed NiFi version
    Navigate to the NiFi UI footer or check the nifi-version.properties file in the NiFi installation directory. The version is typically displayed on the login page or in the about section.
    Affected if The version is between 1.8.0 and 1.21.0 inclusive.
  2. Identify configured JndiJmsConnectionFactoryProvider Controller Services
    In the NiFi UI, go to the Controller Settings (gear icon) and inspect the Controller Services tab. Look for any service with type JndiJmsConnectionFactoryProvider.
    Affected if A JndiJmsConnectionFactoryProvider service exists and is enabled.
  3. Identify flows using ConsumeJMS Processor
    In the NiFi UI, search for processors of type ConsumeJMS. This can be done by adding a processor and searching 'ConsumeJMS' in the processor type search, or by reviewing existing flow configurations.
    Affected if Any ConsumeJMS processor is configured in an active or enabled flow.
  4. Identify flows using PublishJMS Processor
    In the NiFi UI, search for processors of type PublishJMS. This can be done by adding a processor and searching 'PublishJMS' in the processor type search, or by reviewing existing flow configurations.
    Affected if Any PublishJMS processor is configured in an active or enabled flow.
  5. Inspect JNDI configuration in vulnerable components
    For any identified JndiJmsConnectionFactoryProvider, ConsumeJMS, or PublishJMS components, open their configuration and examine the JNDI URL and provider URL properties. Look for any non-standard or external JNDI URLs.
    Affected if The JNDI URL property points to a remote location or uses non-default provider settings.

A user is affected if their NiFi version is 1.8.0-1.21.0 and they have any JndiJmsConnectionFactoryProvider Controller Service, ConsumeJMS Processor, or PublishJMS Processor configured with JNDI settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.21.0
Interim mitigation

Upgrade to Apache NiFi 1.22.0 or later, which implements validation of JNDI URLs and restricts them to an allowed set of schemes.

Recommended fix High confidence

1.22.0 or later

  1. Download Apache NiFi version 1.22.0 or later from the official Apache NiFi distribution site (nifi.apache.org)
  2. Stop the currently running NiFi instance
  3. Back up the existing NiFi installation directory, including configuration files and flow.xml.gz
  4. Extract the new NiFi 1.22.0+ distribution to the target installation location
  5. Migrate any custom configuration files from the backup to the new installation (nifi.properties, bootstrap.conf, authorizers.xml, etc.)
  6. Review and update any custom processors or dependencies that may be affected by the JNDI URL validation changes
  7. Start the NiFi instance
  8. Verify the JndiJmsConnectionFactoryProvider, ConsumeJMS, and PublishJMS components are functioning correctly with the new validation in place
Caveat NiFi upgrades may introduce changes to configuration schemas or API behavior; review release notes for 1.22.0 for any migration requirements

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
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34212 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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