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.

ABTV

// // //
10/30/2017
12:15 PM
Larry Loeb
Larry Loeb
Larry Loeb

CAPTCHA Is Vulnerable

A group of researchers have demonstrated a vulnerability in the widely used CAPTCHA scheme – a vulnerability that may mean the end of CAPTCHA as we know it.

CAPTCHA is an image system that is used by many websites as a way to foil interactions with programs pretending to be humans. It consists of an image field with an object like letters or numbers segmented inside the image. Desegmentizing the characters requires a preexisting understanding of them, which messes up any automated classifiers. They have proven to be useful for years.

One problem, though. Twelve researchers got together and found a way to beat it. They were able to decipher about two thirds of the CAPTCHAs they were given, with a two orders of magnitude less training than was needed by any other previous method that had attempted this.

Their work was just published in Science and outlines how they reproduced the way that an eye functions and the computation that goes on behind the scenes with the information that it sees.

The AI algorithm has components which recognize the edges of viewed shapes, then will categorize the shape. Another part of the AI will take into account the angle at which the shape is being looked at. Only then will another component attempt to match the shape with a standard form of a letter or number (which was stored inside the AI as a Georgia font character).

The researchers call this kind of AI a Recursive Cortical Network (RCN). It is different from other AI CAPTCHA breakers which work on a Convolutional Neural Network (CNN) model. Whereas slight CAPTCHA segmentation changes would throw off a CNN-based decryption, that does not work for RCN.

In one of the scariest sentences in their write-up, the authors say, "RCN breaks the segmentation defense in a fundamental way and with very little training data, which suggests that websites should move to more robust mechanisms for blocking bots." That's academic-speak for: "You guys are hosed."

Websites will need to remind themselves specifically why they don't want automated processes to pass, and do it fairly fast. It may be they don't want a bot to automagically register for services, for example. Putting in a registration limit number for a time period would serve the same purpose, and not be CAPTCHA vulnerable.

Whatever the purpose, the CAPTCHA field is no longer a valid guardian. It can be defeated without signaling that it has been defeated. It is just a small matter of programming for threat actors to incorporate RCN attacks into their actions.

While the front door lock seems to have a new master key out there, security people have to consider the framework around that door and how it can be strengthened. Reviewing why a CAPTCHA field was used in the first place may help in figuring out what next to do.

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
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2597
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2017-2631
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2017-2657
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2017-7527
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2021-41615
PUBLISHED: 2022-08-08
websda.c in GoAhead WebServer 2.1.8 has insufficient nonce entropy because the nonce calculation relies on the hardcoded onceuponatimeinparadise value, which does not follow the secret-data guideline for HTTP Digest Access Authentication in RFC 7616 section 3.3 (or RFC 2617 section 3.2.1). NOTE: 2.1...