Risk
7/15/2013
01:45 PM
Connect Directly
RSS
E-Mail
50%
50%

Chrome Users More Likely To Ignore Security Warnings

Security messages affect user behavior -- as long as they're well-designed, according to study of Chrome and Firefox users.

9 Android Apps To Improve Security, Privacy
9 Android Apps To Improve Security, Privacy
(click image for larger view)
Chrome browser users: Are you feeling invulnerable?

That question seems pertinent after a new study that compared people's reactions to 25 million security warning messages found a curious difference between users of two different types of browsers. Specifically, users continued through 25% of Google Chrome's malware and phishing warnings, but only 10% of equivalent warnings from Mozilla Firefox. Similarly, users clicked through Chrome's SSL warning a whopping 70% of the time, versus only 33% for Firefox.

Those findings were detailed in "Alice in Warningland: A Large-Scale Field Study of Browser Security Warning Effectiveness,", a research paper written by Devdatta Akhawe, a computer science graduate student at the University of California, Berkeley, who recently collaborated on a study to assess the value of bug bounty programs; and Adrienne Porter Felt, who earned her Ph.D. from Berkeley last year and is now a Google research scientist at Google, focusing on Chrome security and privacy problems. Their research is due to be presented at next month's USENIX Security Symposium in Washington.

[ Amazon 1Button extension for Chrome reports user activity back to Amazon. Read more at Jay-Z App, Amazon Extension Slammed On Privacy. ]

The researchers said they gathered their data via Mozilla Firefox and Google Chrome's in-browser telemetry -- which users can enable to share anonymous performance data with the respective browser manufacturers -- which allowed them to observe over 25 million warning impressions in situ. The researchers emphasized, however, that at no time did they have access to personally identifiable information.

The discovery that users react to Chrome and Firefox's warning messages in different ways is good and bad news. The upside is that "security warnings can be effective in practice," the researchers note, and that "the user experience of a warning can have a significant impact on user behavior." That seems to refute the notion that many users simply dismiss warnings and can't be relied on to parse security-related details and come to a safe browsing decision. Or as noted by the authors of Securing Java, in a quotation cited by the "Warningland" report's authors: "Given a choice between dancing pigs and security, the user will pick dancing pigs every time."

But not all warning messages are created equal, as demonstrated by the fact that 70% of Google's SSL warnings were ignored by users, versus only 33% for Firefox users. Either that, or Google Chrome junkies are a bunch of self-selecting danger monkeys.

In fact, the researchers traced some high click-through rates to more advanced users -- namely, users of pre-release or Linux versions of Chrome. "Technically advanced users might feel more confident in the security of their computers, be more curious about blocked websites, or feel patronized by warnings," said the researchers, who recommended further studies of this group of users to help design warnings better tailored to their expectations.

Based on the study results, the researchers said, "The user experience of warnings can have an enormous impact on user behavior, justifying efforts to build usable warnings." They also noted that Google has also begun testing ways to make more Chrome users heed its SSL warnings. "Such a high click-through rate is undesirable: either users are not heeding valid warnings, or the browser is annoying users with invalid warnings and possibly causing warning fatigue."

Another interesting finding was that increasing the number of clicks required to bypass warning messages didn't appear to have any effect. In fact, despite having to click an "advanced" link followed by a "proceed" button, Chrome users still bypassed more warning messages than Firefox users, who had to click only a single, simpler warning. "We find this result surprising," said the researchers. "Common wisdom in e-commerce holds that extra clicks decrease click-through rates -- hence, one-click shopping. Google Chrome's warning designers introduced the extra step in the malware/phishing warning because they expected it to serve as a strong deterrent."

One likely explanation for Chrome's security warning not being as effective is that after a user decides to bypass the warning, up to a certain difficulty level, they simply won't be stopped. Furthermore, few users clicked on Chrome's "more information" link, suggesting that user attention is a finite resource, the researchers said. Accordingly, unless user experience designers get their browser safety messages right, don't expect most users to pay attention.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-2595
Published: 2014-08-31
The device-initialization functionality in the MSM camera driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, enables MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap interface, which all...

CVE-2013-2597
Published: 2014-08-31
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that lever...

CVE-2013-2598
Published: 2014-08-31
app/aboot/aboot.c in the Little Kernel (LK) bootloader, as distributed with Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to overwrite signature-verification code via crafted boot-image load-destination header values that specify memory ...

CVE-2013-2599
Published: 2014-08-31
A certain Qualcomm Innovation Center (QuIC) patch to the NativeDaemonConnector class in services/java/com/android/server/NativeDaemonConnector.java in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.3.x enables debug logging, which allows attackers to obtain sensitive disk-encryption pas...

CVE-2013-6124
Published: 2014-08-31
The Qualcomm Innovation Center (QuIC) init scripts in Code Aurora Forum (CAF) releases of Android 4.1.x through 4.4.x allow local users to modify file metadata via a symlink attack on a file accessed by a (1) chown or (2) chmod command, as demonstrated by changing the permissions of an arbitrary fil...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.