WaratekVRT Sign in
Reset
More filters (2)
Columns
Protection: None✕Vendor org.openrefine✕
Overview 2 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
2matches 0protected0.0% 0exploited0.0% 0CISA KEV0.0% 0public PoC0.0% 0EPSS ≥ 0.50.0%
Protected by Waratek 0 0.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 2 100.0%
Critical 0 0.0% High 0 0.0% Medium 2 100.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 0 0.0% partly blocked 0 0.0% not blocked 2 100.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 2 100.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 1 / month
No exploit published: 2 Medium: 2 not blocked: 2 Proof of concept only: 2
Aug 231 No exploit published1 Medium1 not blocked1 Proof of concept only1 Sep 230 Oct 230 Nov 230 Dec 230 Jan 240 Feb 240 Mar 240 Apr 240 May 240 Jun 240 Jul 240 Aug 240 Sep 240 Oct 241 No exploit published1 Medium1 not blocked1 Proof of concept only1
Aug 23Oct 23Dec 23Feb 24Apr 24Jun 24Aug 24Oct 24
2 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2024-47882 Medium 2024-10-24 No exploit published Proof of concept only 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.
CVE-2022-41401 Medium 2023-08-04 No exploit published Proof of concept only OpenRefine <= v3.5.2 contains a Server-Side Request Forgery (SSRF) vulnerability, which permits unauthorized users to exploit the system, potentially leading to unauthorized access to internal resources and sensitive file disclosure.