Vulnerabilities / Threats

7/23/2018
03:52 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

Software is Achilles Heel of Hardware Cryptocurrency Wallets

Upcoming Black Hat talk will detail software vulnerabilities that can put private cryptocurrency wallets and currency exchange services at risk.

Cryptocurrency exchanges and private wallets have been fully in cyberattacker crosshairs as criminals seek to make the most of an exploding new financial market that some analysts say will reach $1 trillion by the end of the year. In response to these attacks, a number of manufacturers have come out with secure hardware wallets meant to harden the storage of the cryptographic keys that serve as proof of ownership of vast sums of money. However, a new piece of research expected out of Black Hat USA next month shows that these secure hardware storage devices may not be as locked down as their users expect them to be.

Presented by Sergei Volokitin, the research will show how software attacks can be used to break the Secure Element, the supposedly tamper-resistant hardware platform upon which these hardware wallets base their protection. Volokitin found vulnerabilities in these wallets' trusted execution environment (TEE) operating systems that could be manipulated to compromise memory isolation and cause the wallet to give up operating system and application secrets.

"Despite the fact that the device makes use of secure hardware to protect the private keys, a number of flaws in the software design and implementation allowed us to create various attack scenarios, including remote, physical and supply chain attacks," explains Volokitin, who works as a security analyst for Riscure, a global security test lab based in the Netherlands. 

Using the identified vulnerabilities, anybody who can get physical access to the hardware wallet would be able to steal keys and data from the device. What's more, an attacker could theoretically create a supply chain attack where they poison the device from the get-go in order to gain full control of wallets on the device once users started putting data into the hardware's applications. It might sound like a far-fetched attack scenario, but given the stakes it's not unreasonable to consider.

"In cryptocurrency hardware wallets, the stakes are high, since single private key is the only asset preventing an attacker from stealing the coins and getting away with it," says Volokitin.

While particularly troubling for the cryptocurrency ecosystem, Volokitin's research also has broader implications across enterprise security. It's another lesson that hardened secure devices are only as tamper-proof as the firmware and other software embedded within them. 

"Although the hardware wallets are primarily designed to be used in cryptocurrency-related solutions, from a security point of view they are not much different from any other security devices," he says. "In fact, one of the compromised applications on the device was the secure application for FIDO authentication, which can be used in many other applications as well."

He explains that generally it is very difficult for end customers to evaluate the risk of using a hardware security device if it does not require mandatory certification.

"The main questions the end users of such secure devices need to ask themselves/the manufacturer is what manufacturer did to improve the security of the device," he says, explaining they should be looking for vendors that do extensive testing of their hardware products. "Doing an evaluation of a security solution by a third party, through an evaluation or a bug bounty, is an effective way to improve security of a product."

 

 

 

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Google Engineering Lead on Lessons Learned From Chrome's HTTPS Push
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
White Hat to Black Hat: What Motivates the Switch to Cybercrime
Kelly Sheridan, Staff Editor, Dark Reading,  8/8/2018
PGA of America Struck By Ransomware
Dark Reading Staff 8/9/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-3937
PUBLISHED: 2018-08-14
An exploitable command injection vulnerability exists in the measurementBitrateExec functionality of Sony IPELA E Series Network Camera G5 firmware 1.87.00. A specially crafted GET request can cause arbitrary commands to be executed. An attacker can send an HTTP request to trigger this vulnerability...
CVE-2018-3938
PUBLISHED: 2018-08-14
An exploitable stack-based buffer overflow vulnerability exists in the 802dot1xclientcert.cgi functionality of Sony IPELA E Series Camera G5 firmware 1.87.00. A specially crafted POST can cause a stack-based buffer overflow, resulting in remote code execution. An attacker can send a malicious POST r...
CVE-2018-12537
PUBLISHED: 2018-08-14
In Eclipse Vert.x version 3.0 to 3.5.1, the HttpServer response headers and HttpClient request headers do not filter carriage return and line feed characters from the header value. This allow unfiltered values to inject a new header in the client request or server response.
CVE-2018-12539
PUBLISHED: 2018-08-14
In Eclipse OpenJ9 version 0.8, users other than the process owner may be able to use Java Attach API to connect to an Eclipse OpenJ9 or IBM JVM on the same machine and use Attach API operations, which includes the ability to execute untrusted native code. Attach API is enabled by default on Windows,...
CVE-2018-3615
PUBLISHED: 2018-08-14
Systems with microprocessors utilizing speculative execution and Intel software guard extensions (Intel SGX) may allow unauthorized disclosure of information residing in the L1 data cache from an enclave to an attacker with local user access via a side-channel analysis.