Nifi Registry
Approved changes feed: RSS · Atom
cpe:2.3:a:apache:nifi_registry:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Apache (b0303047-b7dd-5cf8-abcc-71b7d9d80b95) |
|---|---|
| Product | Nifi Registry (e8acde66-513d-59da-8318-c19af0d4cb47) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:apache/nifi |
purl2cpe | 2026-06-01 10:14:23.808471 |
pkg:docker/apache/nifi-registry |
purl2cpe | 2026-06-01 10:14:23.808474 |
pkg:github/apache/nifi-registry |
purl2cpe | 2026-06-01 10:14:23.808476 |
pkg:maven/org.apache.nifi.registry/nifi-registry |
purl2cpe | 2026-06-01 10:14:23.808477 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-33140 |
vulnerable | 2026-06-08 05:44:46.288909 |
Improper Neutralization of Command Elements in Shell User Group Provider
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.
Published: 2022-06-15T14:25:15.000Z
Updated: 2024-08-03T08:01:19.873Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-9482 |
vulnerable | 2026-06-08 05:28:01.817440 |
Details available
If NiFi Registry 0.1.0 to 0.5.0 uses an authentication mechanism other than PKI, when the user clicks Log Out, NiFi Registry invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to make API requests to NiFi Registry.
Published: 2020-04-28T18:12:58.000Z
Updated: 2024-08-04T10:26:16.177Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.