Cross-site Scripting (XSS) Affecting rubygem-rake package, versions <0:0.9.2.2-41.el7sat
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Cross-site Scripting (XSS) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-RHEL7-RUBYGEMRAKE-5379274
- published26 Mar 2023
- disclosed4 Apr 2017
Introduced: 4 Apr 2017
CVE-2017-7233 (opens in a new tab)How to fix?
Upgrade RHEL:7 rubygem-rake to version 0:0.9.2.2-41.el7sat or higher.
This issue was patched in RHSA-2018:2927.
NVD Description
Note: Versions mentioned in the description apply only to the upstream rubygem-rake package and not the rubygem-rake package as distributed by RHEL.
See How to fix? for RHEL:7 relevant fixed versions and status.
Django 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the user to an "on success" URL. The security check for these redirects (namely django.utils.http.is_safe_url()) considered some numeric URLs "safe" when they shouldn't be, aka an open redirect vulnerability. Also, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack.