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.

Application Security

10/31/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Google's reCAPTCHA Version 3 Offers Better Bot-Fighting Capabilities

Google is rolling out the third version of reCAPTCHA software, which the company claims can better fight spam and bots with less user input.

reCAPTCHA is the security service hosted by Google that is designed to shield websites from spam and bot traffic. This week, the search giant has announced the latest update -- Version 3 -- that offers new ways of achieving that goal.

Version 3 runs adaptive risk analysis in the background to alert the webmaster of "suspicious" traffic. Google thinks that this new version will let human users enjoy a "frictionless" experience on the site.

Frictionless, as used in this context, means no direct user input is needed, which is a complete change from the previous versions.

What's introduced in the new version is a concept called "Action," which is a tag that can be used to define the key steps of the user journey. These tags will enable reCAPTCHA to run its risk analysis in context.

Since the tags can be placed on multiple pages of the site, reCAPTCHA's adaptive risk analysis engine can identify the pattern of attackers more accurately by looking at the activities that occur across different pages of the website.

In the reCAPTCHA admin console, the webmaster is shown a full overview of reCAPTCHA score distribution, as well as a breakdown for the stats of the Top 10 actions on the site. The console helps identify the pages that are the targets of bot activities.

Google also thinks that there are three potential ways the threat score can be best used:

  • The first is a threshold that determines when a user is to be let through or when further verification needs to be done would be one. Auxiliary methods, such as two-factor authentication and phone verification, could be invoked if the threat level exceeds that threshold.
  • Second, the score can be combined with private signals that reCAPTCHA cannot access. These can include user profiles or transaction histories that could add other data to the "go/no" decision process.
  • Third, the reCAPTCHA score can be incorporated as one of the signals used to train your website's machine learning model for focusing on stopping abuse.

Where the first version of reCAPTCHA that was shut down in March of this year only had one way to test for non-welcome traffic -- displaying skewed text that was resistant to being read by bots -- the latest version allows custom methods to be used.

Of course, Google puts the burden of coming up with those custom methods squarely onto the webmaster. But the new reCAPTCHA version can be invoked as many times as desired using different actions on the same page.

reCAPTCHA also has some implications for Google itself. By using it, the webmaster will provide them with insight into entire flow of a visit and transaction. Now, if the visitor is in Chrome, Google can get both sides of transaction. Remember that Google sign-in that Chrome just started to do?

The more cynical among us might see this new version as a data grab masquerading as a security product.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...