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.

Attacks/Breaches

10/29/2013
08:43 PM
50%
50%

Attackers Crib Exploit Code, But Net Benefit For Defenders

Researcher finds that the top 20 crime packs copy exploit code from security researchers and sophisticated attackers, but doing away with public disclosure is no solution

The crime packs used by criminals to create malware campaigns to compromise and control victims' computers rarely use original attacks, instead relying on reusing techniques found in publicly released exploit code.

An analysis of 18 exploits used by the top 20 crime packs found that the crucial code used in each attack could be traced back to information released by a security researcher, a blog posted by a security firm describing the exploit, or a sophisticated attack created for an espionage campaign. The analysis, presented by Trail of Bits' CEO Dan Guido at last month's BruCon security conference, highlights the dangers that exploit code can pose in a software ecosystem that is slow to patch known vulnerabilities.

"There are pros and cons: The APT groups get by fine totally on their own, they create their own exploits totally in-house, and there is value from a defensive point of view to understanding how these exploits work and what their limitations are," Guido said. "On the other hand, when you see all these security researchers beating up on Java, you know that code is going to slot right into a space waiting for it."

In his analysis, Guido found that eight of the attacks included in the crime packs targeted Adobe Flash and Reader and Internet Explorer, but would only work on Windows XP. Half of the attacks targeted more modern platforms but relied on vulnerabilities in Oracle's Java software platform. Only a single attack, which targeted the Windows TrueType parsing vulnerability, could work on all Windows platforms at the time it was released. That exploit was publicly disclosed in 2011 in an analysis of the Duqu espionage Trojan.

For the most part, the exploits are unreliable and poorly written, he says.

"The only way that these crime packs seem to be able to get really good exploitation capabilities is if they are handed to them on a silver platter by some incredibly complicated and sophisticated APT group," Guido said during his BruCon presentation.

The situation is much different from half a decade ago when the authors of major exploit packs would compete on having unique exploits for certain vulnerabilities in their software, says HD Moore, chief research officer at Rapid7, a vulnerability management firm. Now, once an exploit is publicly discussed, everyone jumps on developing a version of the attacks, he says.

"They need exploits from somewhere, and they might as well use the ones that are available," Moore says. "There is no economic reason why they would go out of their way to build new exploits for what they are doing."

[Windows XP machines six times more likely to be infected by malware than newer versions of the OS, according to new Microsoft Security Intelligence Report (SIR). See Microsoft Software, Overall Operating System Vulnerability Disclosures Rise.]

The data suggests that quashing the publication of exploit code could have a positive effect on the security of the software ecosystem. Yet such approaches have already been tried and largely failed. While defenders have frequently sought to limit the access of criminals and bad actors to the tools needed to circumvent security measures -- such as lock picks and knowledge of safe construction -- software security will not likely benefit from such measures. Software vulnerabilities are often discovered independently, suggesting that silencing the disclosure of a vulnerability and how to exploit the flaw would merely allow a bad actor more time to use an attack, says Darren Meyer, senior security researcher at Veracode, an application security firm.

"It is really important for the disclosure, or even the release of code, to be a possibility," he says. "The legal restraint of that would be a very bad practice."

In addition, attackers' laziness can benefit defenders: The quick adoption of publicly available exploits by the creators of crime packs is also a weakness, says Brian Gorenc, manager of the Zero Day Initiative for HP Security Research.

"The key takeaway here is that a crime pack author’s strength is simultaneously one of its greatest weaknesses," he said in an e-mail interview. "This predictability can give enterprises a leg up on defending their networks."

During his presentation, Trail of Bits' Guido found that a relatively small number of tactics could eliminate much of the risks of crime packs. Companies that opt for more modern platforms are much safer, he says.

"You have all this incremental work going into updating minor versions of applications," he said. "But forget about that -- spend the time on updating to the next major version because then you get the new mitigations."

Eliminating the Java plug-in from the enterprise and using a different browser to access internal resources than is used to surf the Web can also remove known dangers, he said.

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. Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-5216
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.9.0, 5.2.0, and 6.3.0. If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection. Upon seei...
CVE-2020-5217
PUBLISHED: 2020-01-23
In Secure Headers (RubyGem secure_headers), a directive injection vulnerability is present in versions before 3.8.0, 5.1.0, and 6.2.0. If user-supplied input was passed into append/override_content_security_policy_directives, a semicolon could be injected leading to directive injection. This could b...
CVE-2020-5223
PUBLISHED: 2020-01-23
In PrivateBin versions 1.2.0 before 1.2.2, and 1.3.0 before 1.3.2, a persistent XSS attack is possible. Under certain conditions, a user provided attachment file name can inject HTML leading to a persistent Cross-site scripting (XSS) vulnerability. The vulnerability has been fixed in PrivateBin v1.3...
CVE-2019-20399
PUBLISHED: 2020-01-23
A timing vulnerability in the Scalar::check_overflow function in Parity libsecp256k1-rs before 0.3.1 potentially allows an attacker to leak information via a side-channel attack.
CVE-2020-7915
PUBLISHED: 2020-01-22
An issue was discovered on Eaton 5P 850 devices. The Ubicacion SAI field allows XSS attacks by an administrator.