Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Networking (MOSC)

How do you handle CVE-2012-1675

May 3, 2012 12:24AM edited Jul 31, 2020 2:35PM in Database Networking (MOSC) 22 comments

Hi all!
Not very funny in these days...
I've read several articles about the altert CVE-2012-1675 mentioned here http://www.oracle.com/technetwork/topics/security/alert-cve-2012-1675-1608180.html
Now I need to think about how we should solve this problem on hundreds of servers.
I've found the notes about using COST:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1453883.1 (standalone)
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1340831.1 (RAC)

For the first one (standalone), method 1 recommends setting SECURE_REGISTER_<listener_name>=(TCP) in the listener.ora. But fix for bug 12880299

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month