SQL Developer vulnerabilitiesRanked by how likely they are to be used.
SQL Developer is made by Oracle. We track 4 published vulnerabilities in it, across 8 versions. None of them is on the list of flaws known to be exploited today. If you run SQL Developer, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which SQL Developer vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of SQL Developer's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which SQL Developer flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%CVE-2021-45105Medium
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.
- 9.0%CVE-2020-13956Medium
Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request...
- 0.4%
Vulnerability in the SQL Developer Install component of Oracle Database Server.
- 0.2%CVE-2023-21969Medium
Vulnerability in Oracle SQL Developer (component: Installation).
Running SQL Developer? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- SQL Developer on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 4 published vulnerabilities listed under the name SQL Developer, across 8 versions.
None of SQL Developer's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track SQL Developer. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.