CVE-2023-36542: Apache NiFi: Potential Code Injection with Properties Referencing Remote Resources
Noroxi assessment
Priority: Monitor (action score 36/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.9% (FIRST EPSS); higher than 80% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.apache.nifi:nifi-cdc-mysql-bundle (Maven) 1.23.0; org.apache.nifi:nifi-dbcp-service (Maven) 1.23.0; org.apache.nifi:nifi-hadoop-dbcp-service (Maven) 1.23.0.
Low priority for now. Upgrade to org.apache.nifi:nifi-cdc-mysql-bundle (Maven) 1.23.0; org.apache.nifi:nifi-dbcp-service (Maven) 1.23.0; org.apache.nifi:nifi-hadoop-dbcp-service (Maven) 1.23.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Apache NiFi 0.0.2 through 1.22.0 include Processors and Controller Services that support HTTP URL references for retrieving drivers, which allows an authenticated and authorized user to configure a location that enables custom code execution. The resolution introduces a new Required Permission for referencing remote resources, restricting configuration of these components to privileged users. The permission prevents unprivileged users from configuring Processors and Controller Services annotated with the new Reference Remote Resources restriction. Upgrading to Apache NiFi 1.23.0 is the recommended mitigation.
- Published
- Jul 29, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.9% · 80th percentile
- CWE
- CWE-94
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | nifi | cpe:2.3:a:apache:nifi |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache NiFi
- 0.0.2 and later · up to and including 1.22.0affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache nifi0.0.2 and later · up to 1.22.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apache.nifi:nifi-cdc-mysql-bundle | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-dbcp-service | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-hadoop-dbcp-service | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-hbase_2-client-service | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-hikari-dbcp-service | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-jms-processors | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-record-serialization-services | from 0.0.2 · before 1.23.0 | 1.23.0 |
| Maven | org.apache.nifi:nifi-standard-processors | from 0.0.2 · before 1.23.0 | 1.23.0 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-34468Apache NiFi: Potential Code Injection with Database Services using H254Plan
- CVE-2018-1309Apache NiFi External XML Entity issue in SplitXML processor.40Plan
- CVE-2017-15697A malicious X-ProxyContextPath or X-Forwarded-Context header containing external resources or embedded code could cause remote code…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-22832Feb 10, 2023 · Apache NiFi: Improper Restriction of XML External Entity References in ExtractCCDAAttributes30Monitor
- ← EarlierCVE-2023-34212Jun 12, 2023 · Apache NiFi: Potential Deserialization of Untrusted Data with JNDI in JMS Components27Monitor
- Later →CVE-2023-40037Aug 18, 2023 · Apache NiFi: Incomplete Validation of JDBC and JNDI Connection URLs27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.apache.nifi:nifi-cdc-mysql-bundle | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-dbcp-service | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-hadoop-dbcp-service | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-hbase_2-client-service | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-hikari-dbcp-service | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-jms-processors | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-record-serialization-services | 1.23.0 | Package registry (OSV) |
| Maven:org.apache.nifi:nifi-standard-processors | 1.23.0 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2025-08-20 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+753 d
- TodayNov 16, 2026+1206 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- nbxiglkfinder
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-94 · Improper Control of Generation of Code ('Code Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.