Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

6/21/2011
05:09 PM
50%
50%

Malware Increasingly Being Signed With Stolen Certificates

Cybercriminals target legitimate software vendors looking for the keys needed to sign software, helping them defeat security measures

Earlier this year, a Trojan infected a machine at software maker Blackbaud. But rather than steal money or source code or customer details, the attack targeted another valuable but often overlooked piece of information: the company's private keys for signing its software.

Blackbaud, which makes software to help nonprofits run their businesses, discovered the theft when a security firm approached the company and revealed it had encountered malware signed with the company's private keys. Ironically, Blackbaud had already been working to bolster its corporate security, says Jana Eggers, senior vice president of products and marketing for the Charleston, S.C.-based software company.

"Companies are very aware of their customer information, but there are other pieces of information that need to be protected," Eggers says. "A virus can be tweaked to search for something different, and a security certificate is not what you think of protecting in the same way as customer information."

Blackbaud is not alone. Cybercriminals are increasingly targeting developers' systems to steal the private keys used to sign software. Programs signed with a digital certificate are considered safer by the operating system and security software, and the authors of malicious software have caught on.

Perhaps the most high-profile piece of malware to use digital certificates is Stuxnet. The Trojan infected industrial control systems in 2009 and 2010 and is widely considered to have been a nation-state attack on Iran's nuclear processing facility. The first stage of the Stuxnet attack used code signed by certificates belonging to two Taiwanese companies to appear more innocuous to security software.

In 2010, a version of the well-known Zeus banking Trojan used a digital signature belonging to software security firm Kaspersky Labs to lessen the chance of the program being identified as malware. And a third attack in the same year used an Adobe flaw and was signed with a certificate from a credit union.

"They are going right after the keys to the kingdom," says Jeff Hudson, CEO at Venafi, a maker of enterprise key and certificate management software. "They are not trying to siphon off pennies; they are going right for the heart."

Security firm Symantec has documented a piece of malicious software known as Infostealer.Nimkey that is designed to steal private keys and keystrokes.

Thousands of certificates have been stolen and are being used by malware, says Yuval Ben-Itzhak, chief technology officer for security firm AVG. In a quarterly security report released on Tuesday, AVG documented two attacks that used stolen certificates: one belonging to Blackbaud and the other to German gaming company GameForge Productions. GameForge did not respond to a request for comment.

In the first half of 2011, three times as many certificates were used to sign malware than the first half of 2010, according to AVG's report. Companies need to better protect their certificates, and security software should become more skeptical of signed code, Ben-Itzhak says.

"The vendors are not rushing to revoke stolen certificates," he says. "Blindly trusting certificates today is not a good practice."

For large companies, certificate management systems such as Venafi's can make sure that companies do not suffer from certificates that accidentally expire or that are stored in insecure places. Many times, developers just keep the private keys needed to sign software on their work systems, Venafi's Hudson says.

"We advocate people to, number one, know what you've got on your network," he says. "Number two, make sure that you separate out private keys from pubic keys and be able to replace them immediately, if you are compromised."

Treating digital certificates as valuable as the attackers is a sentiment with which Blackbaud's Eggers can now certainly agree. "More people need to be aware of the threat," she says.

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
Modern Day Insider Threat: Network Bugs That Are Stealing Your Data
David Pearson, Principal Threat Researcher,  10/21/2020
Are You One COVID-19 Test Away From a Cybersecurity Disaster?
Alan Brill, Senior Managing Director, Cyber Risk Practice, Kroll,  10/21/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-21269
PUBLISHED: 2020-10-27
checkpath in OpenRC through 0.42.1 might allow local users to take ownership of arbitrary files because a non-terminal path component can be a symlink.
CVE-2020-27743
PUBLISHED: 2020-10-26
libtac in pam_tacplus through 1.5.1 lacks a check for a failure of RAND_bytes()/RAND_pseudo_bytes(). This could lead to use of a non-random/predictable session_id.
CVE-2020-1915
PUBLISHED: 2020-10-26
An out-of-bounds read in the JavaScript Interpreter in Facebook Hermes prior to commit 8cb935cd3b2321c46aa6b7ed8454d95c75a7fca0 allows attackers to cause a denial of service attack or possible further memory corruption via crafted JavaScript. Note that this is only exploitable if the application usi...
CVE-2020-26878
PUBLISHED: 2020-10-26
Ruckus through 1.5.1.0.21 is affected by remote command injection. An authenticated user can submit a query to the API (/service/v1/createUser endpoint), injecting arbitrary commands that will be executed as root user via web.py.
CVE-2020-26879
PUBLISHED: 2020-10-26
Ruckus vRioT through 1.5.1.0.21 has an API backdoor that is hardcoded into validate_token.py. An unauthenticated attacker can interact with the service API by using a backdoor value as the Authorization header.