Skip to content

GHSA-jrcc-7jf5-3pxg CVE-2017-5636

Injection in Apache NiFi

Critical Maven
Severity
9.8 / 10
Critical · CVSS 3.0
Exploit chance (EPSS)
3.60%
Chance of exploitation in the next 30 days. Higher than 89.46% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Fix
0.7.2
Upgrade org.apache.nifi:nifi to this version or later

Description

In Apache NiFi before 0.7.2 and 1.x before 1.1.2 in a cluster environment, the proxy chain serialization/deserialization is vulnerable to an injection attack where a carefully crafted username could impersonate another user and gain their permissions on a replicated request to another node.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.nifi:nifi
< 0.7.2
0.7.2
org.apache.nifi:nifi
>= 1.0.0, < 1.1.2
1.1.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.nifi:nifi Maven → 0.7.2

maven
<dependency><groupId>org.apache.nifi</groupId><artifactId>nifi</artifactId><version>0.7.2</version></dependency>
gradle
implementation("org.apache.nifi:nifi:0.7.2")

Severity breakdown

CVSS 3.0 9.8

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How to prevent it
  • Requirements: Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Implementation: Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-77hf-23pq-2g7c
Code injection in Apache NiFi and NiFi Registry
High Also affects org.apache.nifi:nifi
GHSA-m5r7-w9v3-ghmx
Cross-site Scripting in Apache NiFi
Medium Also affects org.apache.nifi:nifi
GHSA-jvx9-rj3w-jq99
Origin Validation Error in Apache NiFi
High Also affects org.apache.nifi:nifi
GHSA-qj7f-j6h9-g5rq
XML External Entity Reference in Apache NiFi
Medium Also affects org.apache.nifi:nifi
GHSA-29ph-fjf3-c5cm
Apache NiFi XSS issue in context path handling
Critical Also affects org.apache.nifi:nifi
GHSA-w4x6-j349-9r57
Apache NiFi host header poisoning issue
High Also affects org.apache.nifi:nifi
GHSA-p76j-5v6v-6c22
Apache NiFi JMS Deserialization issue
High Also affects org.apache.nifi:nifi
GHSA-g2fm-x3cp-mqw9
Cross-site Scripting in Apache NiFi
Medium Also affects org.apache.nifi:nifi
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor