Solved

Mitigating POODLE on MS SQL Server

Posted on 2015-02-24
1
1,214 Views
Last Modified: 2015-02-25
Hi,

We have some Windows 2008 R2 servers that have had SSL completely disabled via the MS recommended registry change, and the subsequent Nessus scans bore that out as 443 was no longer being flagged for SSL POODLE.  

However, the MS SQL Server running on the same host does still flag that vulnerability during the Nessus scans. I don't seem to be able to get good results using the openssl binary or sslscan to check out the SQL Server port. I also attempted logging into the SQL Server using sqlcmd while running a capture with NetMonitor, and the output would lead me to believe it is not running. Looking at the capture output, I can see where the client attempts a TLS handshake with the client hello, and then there is a client key exchange, followed by an TLS application data packet. Those are the only TLS packets - there were no TLS packets from the server responding to the client so I would think that would indicate TLS/SSL is not being used by the SQL server.

BUT - why would sqlcmd attempt to initiate a TLS handshake if encryption was not enabled, and Tenable states this is not a false positive.

Can anyone help me clear this up. Is there a good, definitive method to determine if SSL is enabled on MS SQL Server? This is assuming SQL Server does not use the system wide SSL/TLS implementation.

Thank you,
Jud
0
Comment
Question by:jpetter
1 Comment
 
LVL 61

Accepted Solution

by:
btan earned 500 total points
Comment Utility
It is not only at the registry for OS level, but also consider configuring it at SQL side for enabling "ForceEncryption" which required you to install a certificate on the server. Likewise, to ensure "Force Protocol Encryption" also on the SQL Server clients, you must have a certificate on the server and the client must have the Trusted Root Authority updated to trust the server certificate. The server would have responded if client start the encryption request as shared. But first have to ensure the provisioning is right at both OS and SQL side.

For 2K8, http://www.mssqltips.com/sqlservertip/3299/how-to-configure-ssl-encryption-in-sql-server/
Still relevant though MS support stated 2K and 2K5 -http://support.microsoft.com/kb/316898
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

SHARE your personal details only on a NEED to basis. Take CHARGE and SECURE your IDENTITY. How do I then PROTECT myself and stay in charge of my own Personal details (and) - MY own WAY...
Many companies are looking to get out of the datacenter business and to services like Microsoft Azure to provide Infrastructure as a Service (IaaS) solutions for legacy client server workloads, rather than continuing to make capital investments in h…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Viewers will learn how the fundamental information of how to create a table.

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now