Oracle 11g Stealth Password Cracking Vulnerability (CVE-2012-3137)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

TeamSHATTER Security Advisory

Oracle 11g Stealth Password Cracking Vulnerability

February 20, 2013

Risk Level:
High

Affected versions:
Oracle Database Server version 11gR1, 11gR2

Remote exploitable:
Yes (No authentication to Database Server is needed)

Credits:
This vulnerability was discovered and researched by Esteban Martinez Fayo of
Application Security Inc.

Details:
There is a flaw in the way that Authentication Session Keys are generated and
protected by Oracle Database Server during the authentication process.  It is
possible to use this flaw to perform unlimited password guesses (cracking) of
any user password in a similar way as if the password hash would be available.
All users that are authenticated by the database using logon protocol version
11 are affected by this vulnerability.  This includes all users created with
the "IDENTIFIED BY" clause, including the SYS user.
The attack can be performed remotely without the need of a valid username and
password.  The attacker just needs to know the SID of the database and the
name of a valid user.  The attack can be done with just a few network packets
and without leaving any trace in native auditing facilities.

Impact:
Remote unauthenticated attackers can perform offline bruteforce on users
passwords, testing millions of passwords per second.

Vendor Status:
Vendor was contacted and a patch was released.

Workaround:
Some possible workarounds:
1) Use strong user passwords. A strong password will make password guessing
more difficult (or impossible) to solve in reasonable time.
2) Use external authentication. Only users that are authenticated by the
database are affected by this vulnerability.  Users that are authentication by
external means are not affected; this includes users authenticated by the
Operating System and the Network (SSL or third-parties like Kerberos).
3) Disable protocol version 11 and use version 10 or lower instead. To do
this, set initialization parameter SEC_CASE_SENSITIVE_LOGON to FALSE.
See https://www.teamshatter.com/?p=3951

 

 for more information about the
workarounds.

Fix:
Apply Oracle Critical Patch Update October 2012 available at Oracle Support.

CVE:
CVE-2012-3137

Links:
http://www.oracle.com/technetwork/topics/security/cpuoct2012-1515893.html

https://www.teamshatter.com/?p=4120

 

https://www.teamshatter.com/?p=3951

 

Timeline:
Vendor Notification - 4/21/2010
Vendor Response - 4/26/2010
Fix - 10/16/2012
Public Disclosure - 2/20/2013
- --
_____________________________________________
Copyright (c) 2013 Application Security, Inc.
http://www.appsecinc.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iEYEARECAAYFAlEmKt8ACgkQRx91imnNIgHM8wCeI7rz04b9jdt/uriRs+Su2m4R
SDUAoJoTdwrJYSfl6aN9Hb+ieGs7dHk9
=yOaN
-----END PGP SIGNATURE-----







Courtesy: securityfocus.com