Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: GSA_kwCzR0hTQS0zd2M1LWZjdzItMjMyOc4AA6Rb
KaTeX missing normalization of the protocol in URLs allows bypassing forbidden protocols
Impact
Code that uses KaTeX's trust
option, specifically that provides a function to block-list certain URL protocols, can be fooled by URLs in malicious inputs that use uppercase characters in the protocol. In particular, this can allow for malicious input to generate javascript:
links in the output, even if the trust
function tries to forbid this protocol via trust: (context) => context.protocol !== 'javascript'
.
Patches
Upgrade to KaTeX v0.16.10 to remove this vulnerability.
Workarounds
- Allow-list instead of block protocols in your
trust
function. - Manually lowercase
context.protocol
viacontext.protocol.toLowerCase()
before attempting to check for certain protocols. - Avoid use of or turn off the
trust
option.
Details
KaTeX did not normalize the protocol
entry of the context
object provided to a user-specified trust
-function, so it could be a mix of lowercase and/or uppercase letters.
It is generally better to allow-list by protocol, in which case this would normally not be an issue. But in some cases, you might want to block-list, and the KaTeX documentation even provides such an example:
Allow all commands but forbid specific protocol:
trust: (context) => context.protocol !== 'file'
Currently KaTeX internally sees file:
and File:
URLs as different protocols, so context.protocol
can be file
or File
, so the above check does not suffice. A simple workaround would be:
trust: (context) => context.protocol.toLowerCase() !== 'file'
Most URL parsers normalize the scheme to lowercase. For example, RFC3986 says:
Permalink: https://github.com/advisories/GHSA-3wc5-fcw2-2329Although schemes are case-insensitive, the canonical form is lowercase and documents that specify schemes must do so with lowercase letters. An implementation should accept uppercase letters as equivalent to lowercase in scheme names (e.g., allow "HTTP" as well as "http") for the sake of robustness but should only produce lowercase scheme names for consistency.
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS0zd2M1LWZjdzItMjMyOc4AA6Rb
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Moderate
Classification: General
Published: 8 months ago
Updated: 8 months ago
CVSS Score: 5.5
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
Identifiers: GHSA-3wc5-fcw2-2329, CVE-2024-28246
References:
- https://github.com/KaTeX/KaTeX/security/advisories/GHSA-3wc5-fcw2-2329
- https://github.com/KaTeX/KaTeX/commit/fc5af64183a3ceb9be9d1c23a275999a728593de
- https://nvd.nist.gov/vuln/detail/CVE-2024-28246
- https://github.com/advisories/GHSA-3wc5-fcw2-2329
Blast Radius: 24.0
Affected Packages
npm:katex
Dependent packages: 1,186Dependent repositories: 23,138
Downloads: 5,949,519 last month
Affected Version Ranges: >= 0.11.0, < 0.16.10
Fixed in: 0.16.10
All affected versions: 0.11.0, 0.11.1, 0.12.0, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.13.8, 0.13.9, 0.13.10, 0.13.11, 0.13.12, 0.13.13, 0.13.14, 0.13.16, 0.13.17, 0.13.18, 0.13.19, 0.13.20, 0.13.21, 0.13.22, 0.13.23, 0.13.24, 0.14.0, 0.14.1, 0.15.0, 0.15.1, 0.15.2, 0.15.3, 0.15.4, 0.15.5, 0.15.6, 0.16.0, 0.16.1, 0.16.2, 0.16.3, 0.16.4, 0.16.5, 0.16.6, 0.16.7, 0.16.8, 0.16.9
All unaffected versions: 0.1.0, 0.1.1, 0.2.0, 0.3.0, 0.4.0, 0.4.3, 0.5.0, 0.5.1, 0.6.0, 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.9.0, 0.10.0, 0.10.1, 0.10.2, 0.16.10, 0.16.11