CVE-2024-32970: Phlex vulnerable to Cross-site Scripting (XSS) via maliciously formed HTML attribute names and values
There is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. The reason these issues were not detected before is the escapes were working as designed. However, their design didn't take into account just how recklessly permissive browser are when it comes to executing unsafe JavaScript via HTML attributes.
Published May 1, 2024 · Updated May 3, 2024
Affected packages
phlex
- Ecosystem
- RubyGems
- Affected
- < 1.9.3
- Fixed in
- 1.9.3
- Check
bundle info phlex
phlex
- Ecosystem
- RubyGems
- Affected
- >= 1.10.0, < 1.10.2
- Fixed in
- 1.10.2
- Check
bundle info phlex
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
There is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data.
The reason these issues were not detected before is the escapes were working as designed. However, their design didn't take into account just how recklessly permissive browser are when it comes to executing unsafe JavaScript via HTML attributes.
Impact
If you render an ` 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 minor versions released in the last year.
If you are on main, it has been patched since `da8f943`
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
Credited to joeldrapper.
References
- https://github.com/phlex-ruby/phlex/security/advisories/GHSA-9p57-h987-4vgx
- https://nvd.nist.gov/vuln/detail/CVE-2024-32970
- https://github.com/phlex-ruby/phlex/commit/da8f94342a84cff9d78c98bcc3b3604ee2e577d2
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy#unsafe-inline
- https://github.com/payloadbox/xss-payload-list
- https://rubygems.org/gems/phlex
- https://rubygems.org/gems/phlex/versions/1.10.2
- https://rubygems.org/gems/phlex/versions/1.9.3
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/phlex/CVE-2024-32970.yml
- https://github.com/advisories/GHSA-9p57-h987-4vgx
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesGHSA-w67g-2h6v-vjgq
Phlex XSS protection bypass via attribute splatting, dynamic tags, and href values
high7.1Feb 6, 2026CVE-2024-32463
Cross-site Scripting (XSS) possible due to improper sanitisation of `href` attributes on `<a>` tags
high7.1Apr 17, 2024CVE-2024-28199
Cross-site Scripting (XSS) possible with maliciously formed HTML attribute names and values in Phlex
high7.1Mar 12, 2024
