What is CVE-2023-36542?

CVE-2023-36542 is a high-severity code injection vulnerability in org.apache.nifi:nifi-cdc-mysql-bundle (maven), affecting versions >= 0.0.2, < 1.23.0. It is fixed in 1.23.0. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2023-36542?

CVE-2023-36542 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2023-36542?

org.apache.nifi:nifi-cdc-mysql-bundle (maven) versions >= 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, < 1.23.0.

Is there a fix for CVE-2023-36542?

Yes. CVE-2023-36542 is fixed in 1.23.0. Upgrade to this version or later.

Is CVE-2023-36542 exploitable, and should I be worried?

Whether CVE-2023-36542 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-36542 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-36542

Q: How severe is CVE-2023-36542?

CVE-2023-36542 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2023-36542?

org.apache.nifi:nifi-cdc-mysql-bundle (maven) versions >= 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, = 0.0.2, < 1.23.0.

Q: Is there a fix for CVE-2023-36542?

Yes. CVE-2023-36542 is fixed in 1.23.0. Upgrade to this version or later.

Q: Is CVE-2023-36542 exploitable, and should I be worried?

Whether CVE-2023-36542 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-36542 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-36542?

Upgrade: org.apache.nifi:nifi-cdc-mysql-bundle to 1.23.0 or later, org.apache.nifi:nifi-jms-processors to 1.23.0 or later, org.apache.nifi:nifi-standard-processors to 1.23.0 or later, org.apache.nifi:nifi-dbcp-service to 1.23.0 or later, org.apache.nifi:nifi-hikari-dbcp-service to 1.23.0 or later, org.apache.nifi:nifi-hadoop-dbcp-service to 1.23.0 or later, org.apache.nifi:nifi-hbase_2-client-service to 1.23.0 or later, org.apache.nifi:nifi-record-serialization-services to 1.23.0 or later.

Summary

Apache NiFi Code Injection vulnerability

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.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2023-36542 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.23.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.nifi:nifi-cdc-mysql-bundle (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-jms-processors (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-standard-processors (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-dbcp-service (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-hikari-dbcp-service (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-hadoop-dbcp-service (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-hbase_2-client-service (>= 0.0.2, < 1.23.0) org.apache.nifi:nifi-record-serialization-services (>= 0.0.2, < 1.23.0)

Security releases

org.apache.nifi:nifi-cdc-mysql-bundle → 1.23.0 (maven) org.apache.nifi:nifi-jms-processors → 1.23.0 (maven) org.apache.nifi:nifi-standard-processors → 1.23.0 (maven) org.apache.nifi:nifi-dbcp-service → 1.23.0 (maven) org.apache.nifi:nifi-hikari-dbcp-service → 1.23.0 (maven) org.apache.nifi:nifi-hadoop-dbcp-service → 1.23.0 (maven) org.apache.nifi:nifi-hbase_2-client-service → 1.23.0 (maven) org.apache.nifi:nifi-record-serialization-services → 1.23.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.nifi:nifi-cdc-mysql-bundle to 1.23.0 or later; org.apache.nifi:nifi-jms-processors to 1.23.0 or later; org.apache.nifi:nifi-standard-processors to 1.23.0 or later; org.apache.nifi:nifi-dbcp-service to 1.23.0 or later; org.apache.nifi:nifi-hikari-dbcp-service to 1.23.0 or later; org.apache.nifi:nifi-hadoop-dbcp-service to 1.23.0 or later; org.apache.nifi:nifi-hbase_2-client-service to 1.23.0 or later; org.apache.nifi:nifi-record-serialization-services to 1.23.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-36542? CVE-2023-36542 is a high-severity code injection vulnerability in org.apache.nifi:nifi-cdc-mysql-bundle (maven), affecting versions >= 0.0.2, < 1.23.0. It is fixed in 1.23.0. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2023-36542? CVE-2023-36542 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2023-36542?
- org.apache.nifi:nifi-cdc-mysql-bundle (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-jms-processors (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-standard-processors (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-dbcp-service (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-hikari-dbcp-service (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-hadoop-dbcp-service (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-hbase_2-client-service (maven) (versions >= 0.0.2, < 1.23.0)
- org.apache.nifi:nifi-record-serialization-services (maven) (versions >= 0.0.2, < 1.23.0)
Is there a fix for CVE-2023-36542? Yes. CVE-2023-36542 is fixed in 1.23.0. Upgrade to this version or later.
Is CVE-2023-36542 exploitable, and should I be worried? Whether CVE-2023-36542 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-36542 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-36542?
- Upgrade org.apache.nifi:nifi-cdc-mysql-bundle to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-jms-processors to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-standard-processors to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-dbcp-service to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-hikari-dbcp-service to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-hadoop-dbcp-service to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-hbase_2-client-service to 1.23.0 or later
- Upgrade org.apache.nifi:nifi-record-serialization-services to 1.23.0 or later