GHSA-3jq8-jg75-rqv6 CVE-2018-17195
Cleartext Transmission of Sensitive Information in Apache nifi
- Severity
- 7.5 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 0.71%
- Chance of exploitation in the next 30 days. Higher than 53.68% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Fix
1.8.0- Upgrade org.apache.nifi:nifi to this version or later
Description
The template upload API endpoint accepted requests from different domain when sent in conjunction with ARP spoofing + man in the middle (MiTM) attack, resulting in a CSRF attack. The required attack vector is complex, requiring a scenario with client certificate authentication, same subnet access, and injecting malicious code into an unprotected (plaintext HTTP) website which the targeted user later visits, but the possible damage warranted a Severe severity level. Mitigation: The fix to apply Cross-Origin Resource Sharing (CORS) policy request filtering was applied on the Apache NiFi 1.8.0 release. Users running a prior 1.x release should upgrade to the appropriate release.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.nifi:nifi | >= 1.0.0, < 1.8.0 |
1.8.0 |
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.8.0
- maven
<dependency><groupId>org.apache.nifi</groupId><artifactId>nifi</artifactId><version>1.8.0</version></dependency>- gradle
implementation("org.apache.nifi:nifi:1.8.0")
Severity breakdown
CVSS 3.0 7.5
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-319: Cleartext Transmission of Sensitive Information
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
How to prevent it
- Architecture and Design: Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
- Implementation: When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
- Implementation: When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
- Testing: Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
- Operation: Configure servers to use encrypted channels for communication, which may include SSL or other secure protocols.
CWE-863: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
- 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 authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
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