First published: Fri Sep 21 2012(Updated: )
The authentication protocol in Oracle Database Server 10.2.0.3, 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.2, and 11.2.0.3 allows remote attackers to obtain the session key and salt for arbitrary users, which leaks information about the cryptographic hash and makes it easier to conduct brute force password guessing attacks, aka "stealth password cracking vulnerability."
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Database | =10.2.0.3 | |
Oracle Database | =10.2.0.4 | |
Oracle Database | =10.2.0.5 | |
Oracle Database | =11.1.0.7 | |
Oracle Database | =11.2.0.2 | |
Oracle Database | =11.2.0.3 | |
Oracle Primavera P6 Enterprise Project Portfolio Management | =8.2 | |
Oracle Primavera P6 Enterprise Project Portfolio Management | =8.3 | |
Oracle Primavera P6 Enterprise Project Portfolio Management | =8.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-3137 has been classified as a high severity vulnerability due to its potential for allowing unauthorized access to user credentials.
To fix CVE-2012-3137, it is essential to update Oracle Database to a patched version that addresses this vulnerability.
CVE-2012-3137 affects various versions of Oracle Database including 10.2.0.3 to 10.2.0.5 and 11.1.0.7 to 11.2.0.3.
CVE-2012-3137 enables attackers to conduct brute force password cracking, compromising user sessions and credentials.
Yes, CVE-2012-3137 specifically affects Oracle Database and Oracle Primavera P6 Enterprise Project Portfolio Management versions stated in the vulnerability details.