« Oracle Critical Patch Update April 2008 is out | Checkpwd 1.23 for MacOS Intel native released »

Oracle CPU April 2008 - Update

Few hours ago Bruce Lowenthal sent me an email that Oracle forgot to inform me what was fixed. Hey how can you forget me. I am reporting bugs since several years… ;-) 6 of my vulnerabilities are now history (if you apply the April patches or a new patchset like 10.2.0.4).3 of the vulnerabilities are the affecting Oracle Spatial. The packages SDO_UTIL [DB05], SDO_GEOM [DB06]  and SDO_IDX [DB07] are vulnerable against SQL Injection. SDO_IDX is also vulnerable in Oracle 11g.

1 vulnerability is a hardcoded default password OUTLN [DB13] for the user OUTLN. In some special cases the Oracle database is resetting the password of the user OUTLN to OUTLN and grants DBA privileges to this user.

The CPU is also fixing 2 PL/SQL injection vulnerabilities from Paul Wright (see Paul’s blog entry). At the moment there is no additional information about vulnerabilities available.

This CPU provides also fixes the the Inline-View and Create-View problem.

Dieser Eintrag wurde am 16 Apr 2008 um 08:05 verfasst und befindet sich in Oracle Security. Sie können alle Antworten zu diesem Eintrag über den Feed RSS 2.0 mitverfolgen. Hinterlassen Sie eine Antwort oder einen Trackback-Link zu Ihrer eigenen Homepage.

| Drucken

2 Antworten auf “Oracle CPU April 2008 - Update”

  1. >zg sagt:
    16 Jun 2008 bei 17:52

    I have a question, how can we exploit injections like SDO_UTIL [DB05], SDO_GEOM [DB06] and SDO_IDX [DB07] when they are defined with AUTHID CURRENT_USER ?

  2. Alexander Kornbrust sagt:
    16 Jun 2008 bei 18:28

    Hello zg,

    I guess you mean privilege escalation. SQL Injection is always a security problem even if privilege escalation is not possible.

    Even if AUTHID=’CURRENT_USER’ privilege escalation is sometimes possible, e.g. KUPW$WORKER, KUPM$MCP, … have all AUTHID=’CURRENT_USER’ and are exploitable.

    Hope this helps.

    Regards

    Alexander

Antwort schreiben

Sie müssen als angemeldet sein, um einen Kommentar schreiben zu können.