phlex makes Cross-site Scripting (XSS) possible due to improper sanitisation of `href` attributes on `<a>` tags
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.10.1, 1.9.2, 1.8.3, 1.7.2, 1.6.3, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- phlex-ruby phlex
From 1.10.0 · fixed in 1.10.1; From 1.9.0 · fixed in 1.9.2; From 1.8.0 · fixed in 1.8.3; From 1.7.0 · fixed in 1.7.2; From 1.6.0 · fixed in 1.6.3; From 1.5.0 · fixed in 1.5.3; From 1.4.0 · fixed in 1.4.2
- phlexRubyGems
From 1.10.0 · fixed in 1.10.1
- phlexRubyGems
From 1.9.0 · fixed in 1.9.2
- phlexRubyGems
From 1.8.0 · fixed in 1.8.3
- phlexRubyGems
From 1.7.0 · fixed in 1.7.2
- phlexRubyGems
From 1.6.0 · fixed in 1.6.3
- phlexRubyGems
From 1.5.0 · fixed in 1.5.3
- phlexRubyGems
fixed in 1.4.2