Endpoint

7/2/2018
12:00 PM
50%
50%

iOS 12 2FA Feature May Carry Bank Fraud Risk

Making two-factor authentication faster could also make it less secure.

A feature in the upcoming iOS 12 release intended to make two-factor authentication easier for users could end up opening some to banking fraud. The potential vulnerability illustrates the risks that come in removing friction from online transactions.

Andreas Gutmann, a researcher at OneSpan’s Cambridge Innovation Centre and a Marie Skłodowska-Curie Actions Fellow of the European Commission, notes that the Security Code Autofill Feature, which will automatically input the security code sent to an iPhone by a two-factor authentication (2FA) scheme, removes the human validation aspect of the transaction signing/authentication process. A human verifying critical information (such as a login attempt) is a critical piece of the 2FA security process; automating the process removes this and could open the user to man-in-the-middle, phishing, or other social engineering attacks.

Apple has stated that the purpose of security code autofill is to speed up the login process and reduce errors. Reducing friction could also increase adoption of 2FA among iPhone users. Gutmann questions whether the benefits are worth the risk and notes that many online banking 2FA schemes provide transaction authentication rather than just user authentication - something that automating the process could endanger.

For more, read here

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14492
PUBLISHED: 2018-07-21
Tenda AC7 through V15.03.06.44_CN, AC9 through V15.03.05.19(6318)_CN, and AC10 through V15.03.06.23_CN devices have a Stack-based Buffer Overflow via a long limitSpeed or limitSpeedup parameter to an unspecified /goform URI.
CVE-2018-3770
PUBLISHED: 2018-07-20
A path traversal exists in markdown-pdf version <9.0.0 that allows a user to insert a malicious html code that can result in reading the local files.
CVE-2018-3771
PUBLISHED: 2018-07-20
An XSS in statics-server <= 0.0.9 can be used via injected iframe in the filename when statics-server displays directory index in the browser.
CVE-2018-5065
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
CVE-2018-5066
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.