CVE-2024-47882
OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project
OpenRefine is a free, open source tool for working with messy data. Prior to version 3.8.3, the built-in "Something went wrong!" error page includes the exception message and exception traceback without escaping HTML tags, enabling injection into the page if an attacker can reliably produce an error with an attacker-influenced message. It appears that the only way to reach this code in OpenRefine itself is for an attacker to somehow convince a victim to import a malicious file, which may be difficult. However, out-of-tree extensions may add their own calls to `respondWithErrorPage`. Version 3.8.3 has a fix for this issue.
Reserved 2024-10-04 | Published 2024-10-24 | Updated 2024-10-25 | Assigner GitHub_Mgithub.com/OpenRefine/OpenRefine/security/advisories/GHSA-j8hp-f2mj-586g
github.com/OpenRefine/OpenRefine/commit/85594e75e7b36025f7b6a67dcd3ec253c5dff8c2
github.com/OpenRefine/OpenRefine/blob/master/main/webapp/modules/core/error.vt
Support options
