| Package | Affected versions | Patched versions |
|---|---|---|
| phlex | ≥ 1.1.0, < 1.1.1≥ 1.2.0, < 1.2.2≥ 1.3.0, < 1.3.3≥ 1.4.0, < 1.4.1≥ 1.5.0, < 1.5.2≥ 1.6.0, < 1.6.2≥ 1.7.0, < 1.7.1≥ 1.8.0, < 1.8.2≥ 1.9.0, < 1.9.1< 1.0.1 | 1.1.11.2.21.3.31.4.11.5.21.6.21.7.11.8.21.9.11.0.1 |
| phlex | = 1.1.0= 1.4.0= 1.7.0= 1.9.0≥ 1.2.0, < 1.2.2≥ 1.3.0, < 1.3.3< 1.0.1 | 1.2.21.3.31.0.1 |
There is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. This was due to improper case-sensitivity in the code that was meant to prevent these attacks.
If you render an <a> tag with an href attribute set to a user-provided link, that link could potentially execute JavaScript when clicked by another user.
a(href: user_profile) { "Profile" }
If you splat user-provided attributes when rendering any HTML or SVG tag, malicious event attributes could be included in the output, executing JavaScript when the events are triggered by another user.
h1(**JSON.parse(user_attributes))
Patches are available on RubyGems for all 1.x minor versions. The patched versions are:
If you are on main, it has been patched since aa50c60
Configuring a Content Security Policy that does not allow unsafe-inline would effectively prevent this vulnerability from being exploited.
In addition to upgrading to a patched version of Phlex, we strongly recommend configuring a Content Security Policy header that does not allow unsafe-inline. Here’s how you can configure a Content Security Policy header in Rails. https://guides.rubyonrails.org/security.html#content-security-policy-header
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free