Database vulnerabilitiesRanked by how likely they are to be used.
Database is made by Oracle. We track 66 published vulnerabilities listed under that exact name, across 14 versions. None of them is on the list of flaws known to be exploited today. Oracle lists newer releases under their own names, such as Database Server, so check those pages too.
We keep watching the known-exploited list.
Is Database listed under other names? Yes.
Oracle also lists Database under more specific names, such as Database Server and Database 10g. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
- Database Server507 published vulnerabilities
- Database 10g37 published vulnerabilities
- Database 9i25 published vulnerabilities
- Database 11g14 published vulnerabilities
- Database 11i8 published vulnerabilities
- Database Mobile/lite Server6 published vulnerabilities
- Database Server Lite3 published vulnerabilities
- Database Lite2 published vulnerabilities
- Database Vault2 published vulnerabilities
- Database Scheduler1 published vulnerability
- Database Assistant1 published vulnerability
- Database Filesystem1 published vulnerability
Which Database vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Database's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Database 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%
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle...
- 95%CVE-2016-2183High
The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to...
- 56%CVE-2020-9484High
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server...
- 18%CVE-2021-25122High
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request...
- 4.8%CVE-2018-1288Medium
In Apache Kafka 0.9.0.0 to 0.9.0.1, 0.10.0.0 to 0.10.2.1, 0.11.0.0 to 0.11.0.2, and 1.0.0, authenticated Kafka users may perform action reserved for the Broker via a manually created fetch request interfering with...
- 3.9%CVE-2019-3740Medium
RSA BSAFE Crypto-J versions prior to 6.2.5 are vulnerable to an Information Exposure Through Timing Discrepancy vulnerabilities during DSA key generation.
- 3.7%CVE-2016-3479High
Unspecified vulnerability in the Portable Clusterware component in Oracle Database Server 11.2.0.4 and 12.1.0.2 allows remote attackers to affect availability via unknown vectors.
- 3.3%CVE-2016-3609Critical
Unspecified vulnerability in the OJVM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote authenticated users to affect confidentiality, integrity, and availability via unknown vectors.
- 2.9%CVE-2016-3454Critical
Unspecified vulnerability in the Java VM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.
Running Database? 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
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the "POODLE" issue.
- Matched to
- Database 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 66 published vulnerabilities listed under the name Database, across 14 versions.
None of Database's vulnerabilities is on the list of flaws known to be exploited today.
Oracle also lists Database under more specific names, such as Database Server and Database 10g. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Database. 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.