WaratekVRT Sign in

Oracle SQL Developer CVEs

2 CVEs, 1 exploited, 1 protected by Waratek

Reset
More filters (2)
Columns
Vendor oracle✕Product sql developer✕
Overview 2 matches · 1 protected · 1 exploited · 0 CISA KEV · 1 public PoC · 1 EPSS ≥ 0.5
2matches 1protected50.0% 1exploited50.0% 0CISA KEV0.0% 1public PoC50.0% 1EPSS ≥ 0.550.0%
Protected by Waratek 1 50.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 50.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 1 50.0% partly blocked 0 0.0% not blocked 1 50.0% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 50.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 1 50.0%
split by peak 1 / month
No exploit published: 1Protected by Waratek: 1 Medium: 2 not blocked: 1blocked by ARMR today: 1 No public exploit: 1Exploited: 1
Dec 211 Protected by Waratek1 Medium1 blocked by ARMR today1 Exploited1 Jan 220 Feb 220 Mar 220 Apr 220 May 220 Jun 220 Jul 220 Aug 220 Sep 220 Oct 220 Nov 220 Dec 220 Jan 230 Feb 230 Mar 230 Apr 231 No exploit published1 Medium1 not blocked1 No public exploit1
Dec 21Feb 22Apr 22Jun 22Aug 22Oct 22Dec 22Feb 23Apr 23
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-2023-21969 Medium 2023-04-18 No exploit published No public exploit Vulnerability in Oracle SQL Developer (component: Installation). Supported versions that are affected are Prior to 23.1.0. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle SQL Developer executes to compromise Oracle SQL Developer. Successful attacks of this vulnerability can result in takeover of Oracle SQL Developer. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).
CVE-2021-45105 Medium 2021-12-18 Protected by Waratek Exploited Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.