GHSA-m379-x4xc-38x9 CVE-2022-3167 PYSEC-2022-268
rdiffweb vulnerable to Improper Restriction of Rendered UI Layers or Frames
- Severity
- 0.0 / 10
- High · CVSS 4.0
- Exploit chance (EPSS)
- 1.17%
- Chance of exploitation in the next 30 days. Higher than 67.32% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-1021 Improper Restriction of Rendered UI Layers or Frames
- Fix
2.4.1- Upgrade rdiffweb to this version or later
Description
rdiffweb prior to 2.4.1 is vulnerable to Improper Restriction of Rendered UI Layers or Frames. This allows attackers to perform clickjacking attacks that can trick victims into performing actions such as entering passwords, liking or deleting posts, and/or initiating an account deletion. This issue has been patched in version 2.4.1.
Affected versions
PyPI
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.
rdiffweb PyPI → 2.4.1
- pip
pip install --upgrade "rdiffweb>=2.4.1"- poetry
poetry add "rdiffweb>=2.4.1"- uv
uv add "rdiffweb>=2.4.1"
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- None
- User interaction
- None
- Confidentiality (vulnerable system)
- High
- Integrity (vulnerable system)
- High
- Availability (vulnerable system)
- High
- Confidentiality (subsequent systems)
- None
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
CVSS 3.1 8.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
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
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-v4gp-hf5j-4566 IKUS Rdiffweb allows an attacker with any valid or stolen access token to act as other users | High | Also affects rdiffweb |
| GHSA-c4rv-2j6x-pq7x Rdiffweb Allocation of Resources Without Limits or Throttling vulnerability | High | Also affects rdiffweb |
| GHSA-wwrg-2w5j-grvx RDiffWeb vulnerable to Allocation of Resources Without Limits or Throttling | Medium | Also affects rdiffweb |
| GHSA-wf33-6x33-wcf9 rdiffweb vulnerable to Authentication Bypass by Primary Weakness | High | Also affects rdiffweb |
| GHSA-m8r9-qxx8-mrxp rdiffweb Improper Access Control vulnerability | Critical | Also affects rdiffweb |
| GHSA-h5wp-jrqc-cwwx rdiffweb vulnerable to Open Redirect | High | Also affects rdiffweb |
| GHSA-83pm-7v48-5jp4 rdiffweb vulnerable to Special Element Injection | Medium | Also affects rdiffweb |
| GHSA-7q4r-x5qg-mmcp rdiffweb has no rate limit on resend email feature | Medium | Also affects rdiffweb |
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