GHSA-2xpp-75vr-22vq CVE-2018-17192
Improper Restriction of Rendered UI Layers or Frames in Apache nifif
- Severity
- 6.5 / 10
- Medium · CVSS 3.0
- Exploit chance (EPSS)
- 2.68%
- Chance of exploitation in the next 30 days. Higher than 85.82% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-1021 Improper Restriction of Rendered UI Layers or Frames
- Fix
1.8.0- Upgrade org.apache.nifi:nifi to this version or later
Description
The X-Frame-Options headers were applied inconsistently on some HTTP responses, resulting in duplicate or missing security headers. Some browsers would interpret these results incorrectly, allowing clickjacking attacks. Mitigation: The fix to consistently apply the security headers 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 6.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Weakness
CWE-1021: Improper Restriction of Rendered UI Layers or Frames
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
How to prevent it
- Implementation: The use of X-Frame-Options allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content. The concept of X-Frame-Options is well documented, but implementation of this protection mechanism is in development to cover gaps. There is a need for allowing frames from multiple domains.
- Implementation: A developer can use a "frame-breaker" script in each page that should not be framed. This is very helpful for legacy browsers that do not support X-Frame-Options security feature previously mentioned. It is also important to note that this tactic has been circumvented or bypassed. Improper usage of frames can persist in the web application through nested frames. The "frame-breaking" script does not intuitively account for multiple nested frames that can be presented to the user.
- Implementation: This defense-in-depth technique can be used to prevent the improper usage of frames in web applications. It prioritizes the valid sources of data to be loaded into the application through the usage of declarative policies. Based on which implementation of Content Security Policy is in use, the developer should use the "frame-ancestors" directive or the "frame-src" directive to mitigate this weakness. Both directives allow for the placement of restrictions when it comes to allowing embedded content.
- Implementation: In addition to frames or iframes as previously mentioned, the web application is expected to place restrictions on whether it is allowed to be rendered within objects, embed, or applet elements.
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