# CVE-2024-28199: Cross-site Scripting (XSS) possible with maliciously formed HTML attribute names and values in Phlex > Attackers can execute JavaScript via malicious HTML attributes in Phlex views, requiring users to upgrade the Ruby library. - **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:** 11 Mar 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-242p-4v39-2v8g ## What is CVE-2024-28199? CVE-2024-28199 is a high-severity cross-site scripting vulnerability in phlex-ruby phlex, published on 11 Mar 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 an open source framework for building object-oriented views in Ruby. 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 `` 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 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 1.x minor versions. Users are advised to upgrade. Users unable to upgrade should consider configuring a content security policy that does not allow `unsafe-inline`. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-28199? 20 open source packages ship an affected version, including phlex. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `phlex` | RubyGems | All versions | 1.0.1 | | `phlex` | RubyGems | All versions | 1.0.1 | | `phlex` | RubyGems | From 1.1.0 | 1.1.1 | | `phlex` | RubyGems | From 1.1.0 | 1.1.1 | | `phlex` | RubyGems | From 1.2.0 | 1.2.2 | | `phlex` | RubyGems | From 1.2.0 | 1.2.2 | | `phlex` | RubyGems | From 1.3.0 | 1.3.3 | | `phlex` | RubyGems | From 1.3.0 | 1.3.3 | | `phlex` | RubyGems | From 1.4.0 | 1.4.1 | | `phlex` | RubyGems | From 1.4.0 | 1.4.1 | | `phlex` | RubyGems | From 1.5.0 | 1.5.2 | | `phlex` | RubyGems | From 1.5.0 | 1.5.2 | | `phlex` | RubyGems | From 1.6.0 | 1.6.2 | | `phlex` | RubyGems | From 1.6.0 | 1.6.2 | | `phlex` | RubyGems | From 1.7.0 | 1.7.1 | | `phlex` | RubyGems | From 1.7.0 | 1.7.1 | | `phlex` | RubyGems | From 1.8.0 | 1.8.2 | | `phlex` | RubyGems | From 1.8.0 | 1.8.2 | | `phlex` | RubyGems | From 1.9.0 | 1.9.1 | | `phlex` | RubyGems | From 1.9.0 | 1.9.1 | Products: Phlex Phlex. ## How do I fix CVE-2024-28199? Upgrade phlex to a fixed version for your release line: 1.0.1, 1.1.1, 1.2.2 or 1.3.3. ## Is CVE-2024-28199 being exploited? There is no known exploitation of CVE-2024-28199 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-28199 and fix it if it is affected. What it is: CVE-2024-28199 is a high-severity cross-site scripting vulnerability in phlex-ruby phlex, published on 11 Mar 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-28199 in the wild and no public exploit code. Affected packages and fixed versions: - phlex (RubyGems): affected all versions; fixed in 1.0.1 - phlex (RubyGems): affected all versions; fixed in 1.0.1 - phlex (RubyGems): affected from 1.1.0; fixed in 1.1.1 - phlex (RubyGems): affected from 1.1.0; fixed in 1.1.1 - phlex (RubyGems): affected from 1.2.0; fixed in 1.2.2 - phlex (RubyGems): affected from 1.2.0; fixed in 1.2.2 - phlex (RubyGems): affected from 1.3.0; fixed in 1.3.3 - phlex (RubyGems): affected from 1.3.0; fixed in 1.3.3 - phlex (RubyGems): affected from 1.4.0; fixed in 1.4.1 - phlex (RubyGems): affected from 1.4.0; fixed in 1.4.1 - phlex (RubyGems): affected from 1.5.0; fixed in 1.5.2 - phlex (RubyGems): affected from 1.5.0; fixed in 1.5.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-28199/ (Markdown: https://insights.sbomify.com/CVE-2024-28199/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28199 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28199 - OSV: https://osv.dev/vulnerability/CVE-2024-28199 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-28199/ Summaries are generated and may contain mistakes; the official description above is the record.