WannaCry is a network worm that exploits a vulnerability in Microsoft's implementation of the SMB protocol. This exploit (codenamed "EternalBlue") has been made available on the internet through the Shadowbrokers dump on April 14th, 2017 and was addressed by Microsoft in their security bulletin MS17-010, along with a subsequently issues patch.
How does WannaCry impact Databases?
The vulnerability is a 'Remote Code Execution' vulnerability that allows an attacker to execute arbitrary code on the attacked host, in short, the attacker can do whatever he/she wants to with the host. For a database server, the attacker can possibly read all data in the database, including sensitive data, change that data, or delete it. In the case of WannaCry, it actually looks for specific database file extensions to encrypt (e.g. .accdb,.dbf, .mdb, .myd, .odb, .sql). Organizations that leverage databases running on vulnerable Windows hosts could experience significant business impact.
What steps can I take to mitigate risk?
Trustwave AppDetectivePRO and DbProtect customers should immediately download and run the "Windows SMB Remote Code Execution Vulnerability (WannaCry ransomware exposure)" SHATTER® Knowledgebase check, which tests if a Windows host is vulnerable to WannaCry and other attacks exploiting the aformentioned vulnerability. Click here to access the check.
What else do I need to do?
Apply missing patches that address known issues, perform regularly scheduled vulnerability assessment scans, schedule (at least) annual penetration tests, and implement security best practices to continuously improve database, network, and application security.
How can Trustwave help?
Trustwave SpiderLabs has issued a special knowledgebase update 5.15 for AppDetectivePRO and DbProtect that adds a new check specifically for WannaCry. Details are enclosed below:
AppDetectivePRO and DbProtect Knowledgebase Update 5.15
New Vulnerability and Configuration Check Highlights
IBM DB2 LUW
Microsoft SQL Server
MySQL
Oracle
Sybase ASE
New Policies
This policy has been created with the guidelines mapped out in the DOD Security Technical Implementation Guides "Oracle Database 11.2g Security Technical Implementation Guide Version 1 Release 11"
This policy has been created with the guidelines mapped out in the DOD Security Technical Implementation Guides "Oracle Database 12c Security Technical Implementation Guide Version 1 Release 7"
This policy has been created with guidance of the configuration parameters outlined by the DISA-STIG Microsoft SQL Server 2012 Security Technical Implementation Guide Version 1, Release 14
This policy has been created with guidance of the configuration parameters outlined by the DISA-STIG Microsoft SQL Server 2014 Security Technical Implementation Guide Version 1, Release 4
Updated Policies
DISA-STIG SQL Server 2012 V1R13 - Audit (Built-In)
Operating System - Audit (Built-in)
User Creation Scripts
Availability