GHSA-3pp3-77j6-8ph6 BIT-nifi-2020-9487 CVE-2020-9487
Missing Authentication for Critical Function in Apache NiFi
High
Maven
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 3.05%
- Chance of exploitation in the next 30 days. Higher than 87.56% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-306 Missing Authentication for Critical Function
- Fix
1.12.0-RC1- Upgrade org.apache.nifi:nifi to this version or later
Description
In Apache NiFi 1.0.0 to 1.11.4, the NiFi download token (one-time password) mechanism used a fixed cache size and did not authenticate a request to create a download token, only when attempting to use the token to access the content. An unauthenticated user could repeatedly request download tokens, preventing legitimate users from requesting download tokens.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.nifi:nifi | >= 1.0.0, < 1.12.0-RC1 |
1.12.0-RC1 |
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 → 1.12.0-RC1
- maven
<dependency><groupId>org.apache.nifi</groupId><artifactId>nifi</artifactId><version>1.12.0-RC1</version></dependency>- gradle
implementation("org.apache.nifi:nifi:1.12.0-RC1")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-306: Missing Authentication for Critical Function
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How to prevent it
- Architecture and Design: Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability. Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port. In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Architecture and Design: Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks. In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
- Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
References
Advisories
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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-jrcc-7jf5-3pxg Injection in Apache NiFi | Critical | 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 |
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