What is CVE-2022-33140?

CVE-2022-33140 is a high-severity OS command injection vulnerability in org.apache.nifi.registry:nifi-registry-core (maven), affecting versions >= 0.6.0, < 1.16.3. It is fixed in 1.16.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2022-33140?

CVE-2022-33140 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-2022-33140?

org.apache.nifi.registry:nifi-registry-core (maven) versions >= 0.6.0, = 1.10.0, < 1.16.3.

Is there a fix for CVE-2022-33140?

Yes. CVE-2022-33140 is fixed in 1.16.3. Upgrade to this version or later.

Is CVE-2022-33140 exploitable, and should I be worried?

Whether CVE-2022-33140 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-2022-33140 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-2022-33140

Q: How severe is CVE-2022-33140?

CVE-2022-33140 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-2022-33140?

org.apache.nifi.registry:nifi-registry-core (maven) versions >= 0.6.0, = 1.10.0, < 1.16.3.

Q: Is there a fix for CVE-2022-33140?

Yes. CVE-2022-33140 is fixed in 1.16.3. Upgrade to this version or later.

Q: Is CVE-2022-33140 exploitable, and should I be worried?

Whether CVE-2022-33140 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-2022-33140 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-2022-33140?

Upgrade: org.apache.nifi.registry:nifi-registry-core to 1.16.3 or later, org.apache.nifi:nifi to 1.16.3 or later.

Summary

Code injection in Apache NiFi and NiFi Registry

The optional ShellUserGroupProvider in Apache NiFi 1.10.0 to 1.16.2 and Apache NiFi Registry 0.6.0 to 1.16.2 does not neutralize arguments for group resolution commands, allowing injection of operating system commands on Linux and macOS platforms. The ShellUserGroupProvider is not included in the default configuration. Command injection requires ShellUserGroupProvider to be one of the enabled User Group Providers in the Authorizers configuration. Command injection also requires an authenticated user with elevated privileges. Apache NiFi requires an authenticated user with authorization to modify access policies in order to execute the command. Apache NiFi Registry requires an authenticated user with authorization to read user groups in order to execute the command. The resolution removes command formatting based on user-provided arguments.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2022-33140 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.16.3); upgrading removes the vulnerable code path.

Affected versions

org.apache.nifi.registry:nifi-registry-core (>= 0.6.0, < 1.16.3) org.apache.nifi:nifi (>= 1.10.0, < 1.16.3)

Security releases

org.apache.nifi.registry:nifi-registry-core → 1.16.3 (maven) org.apache.nifi:nifi → 1.16.3 (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.registry:nifi-registry-core to 1.16.3 or later; org.apache.nifi:nifi to 1.16.3 or later

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

Frequently Asked Questions

What is CVE-2022-33140? CVE-2022-33140 is a high-severity OS command injection vulnerability in org.apache.nifi.registry:nifi-registry-core (maven), affecting versions >= 0.6.0, < 1.16.3. It is fixed in 1.16.3. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2022-33140? CVE-2022-33140 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-2022-33140?
- org.apache.nifi.registry:nifi-registry-core (maven) (versions >= 0.6.0, < 1.16.3)
- org.apache.nifi:nifi (maven) (versions >= 1.10.0, < 1.16.3)
Is there a fix for CVE-2022-33140? Yes. CVE-2022-33140 is fixed in 1.16.3. Upgrade to this version or later.
Is CVE-2022-33140 exploitable, and should I be worried? Whether CVE-2022-33140 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-2022-33140 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-2022-33140?
- Upgrade org.apache.nifi.registry:nifi-registry-core to 1.16.3 or later
- Upgrade org.apache.nifi:nifi to 1.16.3 or later