Perimeter
5/4/2011
11:20 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

How To Respond To The Sony Attacks

How to protect yourself from similar database attacks

You've probably heard that Sony's networks have been hacked. First, the Playstation Network and Qriocity networks were compromised. Just as Sony announced its Welcome Back apology program to customers, it learned that the Sony Entertainment network was compromised as well, exposing millions of user accounts and potentially millions of credit card numbers.

For those in enterprise IT, there is something to learn from these breaches. While it's not entirely clear exactly which method was used, the databases were compromised by either SQL injection (SQLi) or administrative credential compromise. Running unpatched Apache servers gave the attackers additional tools to work with. During the past decade, SQLi, buffer overflows, and password compromises have been the principle ways an attacker compromises a database, so there is nothing new here.

How should you respond? Make sure you fix your stuff!

1) Assessment: Run a vulnerability assessment scan. That will identify missing patches and, depending on the tool you use, quickly identify default password settings. This will detect the critical and high-priority stuff you need to address.

2) Passwords: Change all database administration passwords and generic application account passwords using complex passwords. Even if they are not at the default settings, change them anyway. This is easy to do. Also, change the password your Web application uses to connect to the database. It makes it nearly impossible for an attacker to guess, or even "brute force" your database passwords. If you are worried about remembering the passwords -- or even coming up with good random passwords -- then use a tool like 1Password to generate them, and then store them on your phone or iPad so you have them handy. That way are not worried about remembering 30-character random strings.

3) Patch: This is achieved with medium difficulty. The vulnerability scan will identify what patches are missing, or check with your database vendor. This closes the known code-injection attacks against the database and renders most off-the-shelf malware useless.

4) Validate Input: Verify input parameter validation. This involves a high degree of difficulty if your development teams don't already do this. You'll need to either perform white box code analysis or a Web application vulnerability scan to detect unfiltered input values, and then get the application development team to fix them. Optionally, you can use stored procedures instead of SQL statements -- which will take a very long time to implement depending on the size of your application -- or look into Web application firewalls as a quick fix to block known attacks. But the best course of action is to ensure you filter all input values prior to passing them to the database.

Close these three gaps and you cover 98 percent of the avenues attackers use to gain access to databases, greatly reducing your overall risk.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-5395
Published: 2014-11-21
Multiple cross-site request forgery (CSRF) vulnerabilities in Huawei HiLink E3276 and E3236 TCPU before V200R002B470D13SP00C00 and WebUI before V100R007B100D03SP01C03, E5180s-22 before 21.270.21.00.00, and E586Bs-2 before 21.322.10.00.889 allow remote attackers to hijack the authentication of users ...

CVE-2014-7137
Published: 2014-11-21
Multiple SQL injection vulnerabilities in Dolibarr ERP/CRM before 3.6.1 allow remote authenticated users to execute arbitrary SQL commands via the (1) contactid parameter in an addcontact action, (2) ligne parameter in a swapstatut action, or (3) project_ref parameter to projet/tasks/contact.php; (4...

CVE-2014-7871
Published: 2014-11-21
SQL injection vulnerability in Open-Xchange (OX) AppSuite before 7.4.2-rev36 and 7.6.x before 7.6.0-rev23 allows remote authenticated users to execute arbitrary SQL commands via a crafted jslob API call.

CVE-2014-8090
Published: 2014-11-21
The REXML parser in Ruby 1.9.x before 1.9.3 patchlevel 551, 2.0.x before 2.0.0 patchlevel 598, and 2.1.x before 2.1.5 allows remote attackers to cause a denial of service (CPU and memory consumption) a crafted XML document containing an empty string in an entity that is used in a large number of nes...

CVE-2014-8469
Published: 2014-11-21
Cross-site scripting (XSS) vulnerability in Guests/Boots in AdminCP in Moxi9 PHPFox before 4 Beta allows remote attackers to inject arbitrary web script or HTML via the User-Agent header.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?