bugtraq - Re: The history of a -probably- 13 years old Oracle bug: TNS Poison

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <201204261235.q3QCZvxg018251@sf01web2.securityfocus.com>
Date: Thu, 26 Apr 2012 12:35:57 GMT
From: laurenz.albe@...n.gv.at
To: bugtraq@...urityfocus.com
Subject: Re: The history of a -probably- 13 years old Oracle bug: TNS Poison

I wanted to comment on the workarounds for this problem:

1) Setting SQLNET.ENCRYPTION_SERVER=REQUIRED on the server is not enough to protect you.
   To avoid "man in the middle" attacks, you need to have an SSL certificate on
   the server and SSL_SERVER_DN_MATCH=TRUE in the client's sqlnet.ora.

2) Another way to protect yourself in Oracle 11.1 or better is to configure the listener
   to only accept registration requests from the local machine by adding
   SECURE_REGISTER_<listener>=(IPC) to listener.ora.
   The databases must be configured with LOCAL_LISTENER='(ADDRESS=(PROTOCOL=IPC)(KEY=<like in listener.ora>))'

Yours,
Laurenz Albe