Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Mitigating POODLE on MS SQL Server

Posted on 2015-02-24
1
Medium Priority
?
1,628 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 64

Accepted Solution

by:
btan earned 2000 total points
ID: 40630019
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

Looking for the Wi-Fi vendor that's right for you?

We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
When trying to connect from SSMS v17.x to a SQL Server Integration Services 2016 instance or previous version, you get the error “Connecting to the Integration Services service on the computer failed with the following error: 'The specified service …
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

721 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