# CVE-2024-32970: Cross-site Scripting (XSS) possible with maliciously formed HTML attribute names and values in Phlex > Attackers can execute arbitrary JavaScript via malicious HTML attributes in Phlex views, requiring upgrades or CSP configuration. - **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 Apr 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-9p57-h987-4vgx ## What is CVE-2024-32970? CVE-2024-32970 is a high-severity cross-site scripting vulnerability in phlex-ruby phlex, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Phlex is a framework for building object-oriented views in Ruby. In affected versions there is a potential cross-site scripting (XSS) vulnerability that can be exploited via maliciously crafted user data. Since the last two vulnerabilities https://github.com/phlex-ruby/phlex/security/advisories/GHSA-242p-4v39-2v8g and https://github.com/phlex-ruby/phlex/security/advisories/GHSA-g7xq-xv8c-h98c, we have invested in extensive browser tests. It was these new tests that helped us uncover these issues. As of now the project exercises every possible attack vector the developers can think of — including enumerating every ASCII character, and we run these tests in Chrome, Firefox and Safari. Additionally, we test against a list of 6613 known XSS payloads (see: payloadbox/xss-payload-list). 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 browsers are when it comes to executing unsafe JavaScript via HTML attributes. 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. 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. Patches are available on RubyGems for all minor versions released in the last year. Users are advised to upgrade. Users unable to upgrade should configure a Content Security Policy that does not allow `unsafe-inline` which would effectively prevent this vulnerability from being exploited. Users who upgrade are also advised to configure a Content Security Policy header that does not allow `unsafe-inline`. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-32970? 4 open source packages ship an affected version, including phlex. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `phlex` | RubyGems | All versions | 1.9.3 | | `phlex` | RubyGems | All versions | 1.9.3 | | `phlex` | RubyGems | From 1.10.0 | 1.10.2 | | `phlex` | RubyGems | From 1.10.0 | 1.10.2 | ## How do I fix CVE-2024-32970? Upgrade phlex to a fixed version for your release line: 1.9.3 or 1.10.2. ## Is CVE-2024-32970 being exploited? There is no known exploitation of CVE-2024-32970 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32970 and fix it if it is affected. What it is: CVE-2024-32970 is a high-severity cross-site scripting vulnerability in phlex-ruby phlex, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-32970 in the wild and no public exploit code. Affected packages and fixed versions: - phlex (RubyGems): affected all versions; fixed in 1.9.3 - phlex (RubyGems): affected all versions; fixed in 1.9.3 - phlex (RubyGems): affected from 1.10.0; fixed in 1.10.2 - phlex (RubyGems): affected from 1.10.0; fixed in 1.10.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32970/ (Markdown: https://insights.sbomify.com/CVE-2024-32970/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32970 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32970 - OSV: https://osv.dev/vulnerability/CVE-2024-32970 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32970/ Summaries are generated and may contain mistakes; the official description above is the record.