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.

Threat Intelligence

11/22/2017
10:00 AM
50%
50%

Samsung Pay Leaks Mobile Device Information

Researcher at Black Hat Europe will show how Samsung Pay's security falls short and ways attackers could potentially bypass it.

Mobile users installing Samsung Pay on their devices could have sensitive information stolen by attackers due to a newly discovered weakness in the app that leaks the digital tokens that secure transactions and other technical information such as network traffic logs.

An attacker could capture this information without having to authenticate to the device, according to a Tencent researcher who goes by the name of HC, who at Black Hat Europe 2017 next month will present his findings on the Samsung Pay security weaknesses.

"This information can let the attacker learn much more about the internal mechanisms of Samsung Pay and allow them to use it to their advantage to go even deeper into Samsung Pay," HC says.

The attacker, for example, could take the information and use it to view communication between users and their banks in plain text. With enough information, HC notes, an attacker could create another token to withdraw money from users' bank accounts.

Samsung Pay's tokens are unique alphanumeric identifiers generated via algorithms and designed to eliminate the need to use a credit card or debit card number.

"This is not a vulnerability in Samsung Pay, but a mistake in Samsung Pay's app. The mistake is you don't need privileges to get access to the phone log system," says HC, who has notified Samsung about the issue.

HC conducted his research using a Samsung Galaxy S6 but says all Samsung Galaxy smartphones that feature Samsung Pay may be at risk.

The purpose of HC's presentation is to discuss Samsung Pay's security and how to generate a token without the device being physically present, which is different than a 2016 Black Hat Samsung Pay demonstration by another security researcher, HC notes.

Although HC in his research had aimed to generate a token without a Samsung Galaxy device, he acknowledged he was not able to achieve that goal because of the strength of the encrypted traffic and difficulty in accessing the secure chip to crack the encrypted key.

"It is possible to compromise Samsung Pay with the right tools and skills," HC says, noting in his particular case the desired tools were not immediately available.

Related Content:

 

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Tor Weaponized to Steal Bitcoin
Dark Reading Staff 10/18/2019
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
State of SMB Insecurity by the Numbers
Ericka Chickowski, Contributing Writer,  10/17/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-9501
PUBLISHED: 2019-10-22
The Artificial Intelligence theme before 1.2.4 for WordPress has XSS because Genericons HTML files are unnecessarily placed under the web root.
CVE-2019-16971
PUBLISHED: 2019-10-22
In FusionPBX up to 4.5.7, the file app\messages\messages_thread.php uses an unsanitized "contact_uuid" variable coming from the URL, which is reflected on 3 occasions in HTML, leading to XSS.
CVE-2019-16972
PUBLISHED: 2019-10-22
In FusionPBX up to 4.5.7, the file app\contacts\contact_addresses.php uses an unsanitized "id" variable coming from the URL, which is reflected in HTML, leading to XSS.
CVE-2019-16973
PUBLISHED: 2019-10-22
In FusionPBX up to 4.5.7, the file app\contacts\contact_edit.php uses an unsanitized "query_string" variable coming from the URL, which is reflected in HTML, leading to XSS.
CVE-2015-9496
PUBLISHED: 2019-10-22
The freshmail-newsletter plugin before 1.6 for WordPress has shortcode.php SQL Injection via the 'FM_form id=' substring.