Oracle10g vulnerabilitiesRanked by how likely they are to be used.

Product27 versions
The short answer

Oracle10g is made by Oracle. We track 23 published vulnerabilities in it, across 27 versions. None of them is on the list of flaws known to be exploited today. If you run Oracle10g, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Oracle10g vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Oracle10g's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Oracle10g 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.

50% or more10% to 49%Under 10%
  1. 43%

    SQL injection vulnerability in the Oracle Database Server 10g allows remote authenticated users to execute arbitrary SQL commands with elevated privileges via the SUBSCRIPTION_NAME parameter in the (1)...

    CVSS7.5Published31 Dec 2005
  2. 38%

    The DBMS_Scheduler in Oracle 10g allows remote attackers with CREATE JOB privileges to gain additional privileges by changing SESSION_USER to the SYS user.

    CVSS4.6Published11 May 2005
  3. 15%

    Oracle 10g Database Server stores the password for the SYSMAN account in cleartext in the world-readable emoms.properties file, which could allow local users to gain DBA privileges.

    CVSS4.6Published4 Aug 2004
  4. 14%

    Directory traversal vulnerability in extproc in Oracle 9i and 10g allows remote attackers to access arbitrary libraries outside of the $ORACLE_HOME\bin directory.

    CVSS8.5Published4 Aug 2004
  5. 11%

    Stack-based buffer overflow in Oracle 9i and 10g allows remote attackers to execute arbitrary code via a long token in the text of a wrapped procedure.

    CVSS9.0Published4 Aug 2004
  6. 9.0%

    The PL/SQL module for the Oracle HTTP Server in Oracle Application Server 10g, when using the WE8ISO8859P1 character set, does not perform character conversions properly, which allows remote attackers to bypass...

    CVSS7.5Published4 Aug 2004
  7. 7.4%

    Extproc in Oracle 9i and 10g does not require authentication to load a library or execute a function, which allows local users to execute arbitrary commands as the Oracle user.

    CVSS4.6Published4 Aug 2004
  8. 7.3%

    Oracle 10g Database Server, when installed with a password that contains an exclamation point ("!") for the (1) DBSNMP or (2) SYSMAN user, generates an error that logs the password in the world-readable...

    CVSS4.4Published4 Aug 2004
  9. 6.5%

    Multiple SQL injection vulnerabilities in Oracle 10g Release 1 before CPU Jan 2006 allow remote attackers to execute arbitrary SQL commands via multiple parameters in (1) ATTACH_JOB, (2) HAS_PRIVS, and (3) OPEN_JOB...

    CVSS7.5Published8 Feb 2006
Precursor Intelligence

Running Oracle10g? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 23 published vulnerabilities listed under the name Oracle10g, across 27 versions.

None of Oracle10g's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Oracle10g. 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.