phlex 0.2.2
Cross-site Scripting (XSS) possible due to improper sanitisation of href
attributes on <a>
tags
~> 1.4.2
, ~> 1.5.3
, ~> 1.6.3
, ~> 1.7.2
, ~> 1.8.3
, ~> 1.9.2
, >= 1.10.1
Summary
There is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data.
Our filter to detect and prevent the use of the javascript:
URL scheme in the href
attribute of an <a>
tag could be bypassed with tab \t
or newline \n
characters between the characters of the protocol, e.g. java\tscript:
.
Impact
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" }
Mitigation
The best way to mitigate this vulnerability is to update to one of the following versions:
Workarounds
Configuring a Content Security Policy that does not allow unsafe-inline
would effectively prevent this vulnerability from being exploited.
Cross-site Scripting (XSS) possible with maliciously formed HTML attribute names and values in Phlex
high severity CVE-2024-28199~> 1.0.1
, ~> 1.1.1
, ~> 1.2.2
, ~> 1.3.3
, ~> 1.4.1
, ~> 1.5.2
, ~> 1.6.2
, ~> 1.7.1
, ~> 1.8.2
, >= 1.9.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.
Impact
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
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
Workarounds
Configuring a Content Security Policy
that does not allow unsafe-inline
would effectively prevent this vulnerability from being exploited.
References
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
No officially reported memory leakage issues detected.
This gem version does not have any officially reported memory leaked issues.
No license issues detected.
This gem version has a license in the gemspec.
This gem version is available.
This gem version has not been yanked and is still available for usage.