OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpenRefine | OpenRefine | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-3067 | 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. |
Github GHSA |
GHSA-j8hp-f2mj-586g | OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project |
Ubuntu USN |
USN-7260-1 | OpenRefine vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.510% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openrefine
Openrefine openrefine |
|
| CPEs | cpe:2.3:a:openrefine:openrefine:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Openrefine
Openrefine openrefine |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | OpenRefine's error page lacks escaping, leading to potential Cross-site Scripting on import of malicious project | |
| Weaknesses | CWE-79 CWE-81 |
|
| References |
| |
| Metrics |
cvssV3_1
|