CVE-2024-37166: ghtml Cross-Site Scripting (XSS) vulnerability
Summary It is possible to introduce user-controlled JavaScript code and trigger a Cross-Site Scripting (XSS) vulnerability in some cases. Actions Taken - Updated the documentation to clarify that while ghtml escapes characters with special meaning in HTML, it does not provide comprehensive protection against all types of XSS attacks in every scenario. This aligns with the approach taken by other template engines.
Published Jun 10, 2024 · Updated Jun 11, 2024
Affected packages
ghtml
- Ecosystem
- npm
- Affected
- < 2.0.0
- Fixed in
- 2.0.0
- Check
npm ls ghtml
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
It is possible to introduce user-controlled JavaScript code and trigger a Cross-Site Scripting (XSS) vulnerability in some cases.
Actions Taken
- Updated the documentation to clarify that while
ghtmlescapes characters with special meaning in HTML, it does not provide comprehensive protection against all types of XSS attacks in every scenario. _This aligns with the approach taken by other template engines. Developers should be cautious and take additional measures to sanitize user input and prevent potential vulnerabilities._ More reading: https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html - The backtick character (`) is now also escaped to prevent the creation of strings in most cases where a malicious actor somehow gains the ability to write JavaScript. This does not provide comprehensive protection either.
Credited to lirantal.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
