# CVE-2024-32463: phlex makes Cross-site Scripting (XSS) possible due to improper sanitisation of `href` attributes on `<a>` tags

> An XSS vulnerability in the Phlex Ruby framework allows attackers to execute scripts via bypassed href sanitization, requiring an upgrade to patched versions.

- **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:** 17 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-g7xq-xv8c-h98c

## What is CVE-2024-32463?

CVE-2024-32463 is a high-severity cross-site scripting vulnerability in phlex-ruby phlex, published on 17 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 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. The 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:`. This vulnerability is fixed in 1.10.1, 1.9.2, 1.8.3, 1.7.2, 1.6.3, 1.5.3, and 1.4.2. Configuring a Content Security Policy that does not allow `unsafe-inline` would effectively prevent this vulnerability from being exploited.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-32463?

14 open source packages ship an affected version, including phlex.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phlex` | RubyGems | All versions | 1.4.2 |
| `phlex` | RubyGems | All versions | 1.4.2 |
| `phlex` | RubyGems | From 1.10.0 | 1.10.1 |
| `phlex` | RubyGems | From 1.10.0 | 1.10.1 |
| `phlex` | RubyGems | From 1.5.0 | 1.5.3 |
| `phlex` | RubyGems | From 1.5.0 | 1.5.3 |
| `phlex` | RubyGems | From 1.6.0 | 1.6.3 |
| `phlex` | RubyGems | From 1.6.0 | 1.6.3 |
| `phlex` | RubyGems | From 1.7.0 | 1.7.2 |
| `phlex` | RubyGems | From 1.7.0 | 1.7.2 |
| `phlex` | RubyGems | From 1.8.0 | 1.8.3 |
| `phlex` | RubyGems | From 1.8.0 | 1.8.3 |
| `phlex` | RubyGems | From 1.9.0 | 1.9.2 |
| `phlex` | RubyGems | From 1.9.0 | 1.9.2 |

## How do I fix CVE-2024-32463?

Upgrade phlex to a fixed version for your release line: 1.4.2, 1.10.1, 1.5.3 or 1.6.3.

## Is CVE-2024-32463 being exploited?

There is no known exploitation of CVE-2024-32463 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32463 and fix it if it is affected.

What it is: CVE-2024-32463 is a high-severity cross-site scripting vulnerability in phlex-ruby phlex, published on 17 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-32463 in the wild and no public exploit code.

Affected packages and fixed versions:
- phlex (RubyGems): affected all versions; fixed in 1.4.2
- phlex (RubyGems): affected all versions; fixed in 1.4.2
- phlex (RubyGems): affected from 1.10.0; fixed in 1.10.1
- phlex (RubyGems): affected from 1.10.0; fixed in 1.10.1
- phlex (RubyGems): affected from 1.5.0; fixed in 1.5.3
- phlex (RubyGems): affected from 1.5.0; fixed in 1.5.3
- phlex (RubyGems): affected from 1.6.0; fixed in 1.6.3
- phlex (RubyGems): affected from 1.6.0; fixed in 1.6.3
- phlex (RubyGems): affected from 1.7.0; fixed in 1.7.2
- phlex (RubyGems): affected from 1.7.0; fixed in 1.7.2
- phlex (RubyGems): affected from 1.8.0; fixed in 1.8.3
- phlex (RubyGems): affected from 1.8.0; fixed in 1.8.3

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-32463/ (Markdown: https://insights.sbomify.com/CVE-2024-32463/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32463
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32463
- OSV: https://osv.dev/vulnerability/CVE-2024-32463

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32463/
Summaries are generated and may contain mistakes; the official description above is the record.