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
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Major International Airport System Access Sold for $10 on Dark Web
Kelly Sheridan, Staff Editor, Dark Reading,  7/11/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-14373
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. In TIFFFindField in tif_dirinfo.c, the structure tif is being dereferenced without first checking that the structure is not empty and has the requested fields (tif_foundfield). In the call sequences following from the affected library functions (TIFFVGetFiel...
CVE-2018-14374
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow can occur via an empty fmt argument to unixErrorHandler in tif_unix.c, and it can be exploited (at a minimum) via the following high-level library API functions: TIFFClientOpen, TIFFFdOpen, TIFFRawStripSize, TIFFCheckTile, TIFFComputeStrip,...
CVE-2018-14375
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow vulnerability can occur via an invalid or empty tif argument to TIFFRGBAImageOK in tif_getimage.c, and it can be exploited (at a minimum) via the following high-level library API functions: TIFFReadRGBAImage, TIFFRGBAImageOK, and TIFFRGBAIm...
CVE-2018-14378
PUBLISHED: 2018-07-17
An issue was discovered in LibTIFF 4.0.9. A buffer overflow can occur via an invalid or empty tif argument to TIFFWriteBufferSetup in tif_write.c, and it can be exploited (at a minimum) via the following high-level library API function: TIFFWriteTile.
CVE-2018-14363
PUBLISHED: 2018-07-17
An issue was discovered in NeoMutt before 2018-07-16. newsrc.c does not properly restrict '/' characters that may have unsafe interaction with cache pathnames.