Vulnerabilities / Threats

3/7/2018
12:24 PM
50%
50%

Memcached DDoS Attack: Kill Switch, New Details Disclosed

Corero shares a kill switch for the Memcached vulnerability and reports the flaw is more extensive than originally believed.

Corero Network Security has disclosed a "kill switch" for the Memcached vulnerability to national security agencies and shared new evidence indicating the flaw is more dangerous than previously believed. For the first time, threat actors have been exploiting unsecured Memcached servers to launch distributed denial-of-service (DDoS) attacks on target businesses.

Memcached is an open-source memory caching system that stores data in RAM to accelerate access times. It was not built for Internet access; users don't have to authenticate. This exploit lets attackers create spoof requests and boost attacks up to 50,000 times.

The attacks, which hit businesses including GitHub, started in late February. German DDoS mitigation service provider Link11 was among the first to report the new activity, which included UDP attacks using Memcached servers to spread. Link11 found 5,000 vulnerable Memcached servers on the public internet.

Corero researchers have discovered that any exposed Memcached server that can be leveraged for a DDoS attack can also be tricked into sharing user data it has cached from its local network or host. Because Memcached servers don't require authentication, anything added to a vulnerable server can be stolen. Attackers can also modify data and reinsert it in the cache without owners' knowledge.

The "kill switch" sends a command back to the attackers' server to suppress the current DDoS exploitation. This invalidates the cache of a vulnerable server, including attackers' potentially malicious payload. It has been effectively tested on live attacking servers, Corero reports.

Read more details here.

 

 

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

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
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Microsoft Fixes 11 Critical, 39 Important Vulns
Kelly Sheridan, Staff Editor, Dark Reading,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-1060
PUBLISHED: 2018-06-18
python before versions 2.7.15, 3.4.9, 3.5.6 and 3.7.0 is vulnerable to catastrophic backtracking in pop3lib's apop() method. An attacker could use this flaw to cause denial of service.
CVE-2018-1090
PUBLISHED: 2018-06-18
In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. An attacker with API access can then view these secrets.
CVE-2018-1152
PUBLISHED: 2018-06-18
libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.
CVE-2018-1153
PUBLISHED: 2018-06-18
Burp Suite Community Edition 1.7.32 and 1.7.33 fail to validate the server certificate in a couple of HTTPS requests which allows a man in the middle to modify or view traffic.
CVE-2018-12530
PUBLISHED: 2018-06-18
An issue was discovered in MetInfo 6.0.0. admin/app/batch/csvup.php allows remote attackers to delete arbitrary files via a flienamecsv=../ directory traversal. This can be exploited via CSRF.