Development team spells out mitigation strategies for DDoS threat in advance of patch release.
A working proof-of-concept christened the "Apache Killer" released this week uses an as-yet unpatched flaw in the server software that pounds Apache servers with a distributed denial of service (DDoS) attack--and all it would take is one machine to bring the server to its knees.
The Apache development team late Wednesday issued an alert and workarounds in advance of rolling out a patch for the flaw in Apache HTTPD Web Server 1.3 and 2.X. The Apache Killer lets an attacker use a single PC to wage a denial of service attack against an Apache server.
"By sending specially crafted HTTP requests which include malformed range HTTP header, an attacker can disrupt the normal function of the Web server, thus disallowing legitimate users to receive responses from the Web server," the team's advisory said. "This issue affects all Apache software versions and a patch has not been released yet."
The underlying flaw was apparently first reported on bugtraq in 2007. "It appears due to its lack of sophistication that it did not get much attention by Apache developers and it has remained unpatched all of this time," wrote Kevin Shortt of the SANS Internet Storm Center, who noted that he had not yet tested the proof of concept (PoC), but planned to.
Meanwhile, vendors were stepping forward Thursday announcing their protections against the Apache Killer attack.
Sourcefire said its IPS and open-source Snort technology have been able to detect this flaw for several years and that its vulnerability research team Thursday beefed up that protection with a new rule specific to the Apache Killer.
The vendors, contractors, and other outside parties with which you do business can create a serious security risk. Here's how to keep this threat in check. Also in the new, all-digital issue of Dark Reading: Why focusing solely on your own company's security ignores the bigger picture. Download it now. (Free registration required.)
Published: 2014-08-29 Monitoring Agent for UNIX Logs 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, and 6.2.3 through FP04 and Monitoring Server (ms) and Shared Libraries (ax) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP08, 6.2.3 through FP01, and 6.3.0 through FP01 in IBM Tivoli Monitoring (ITM)...
Published: 2014-08-29 FileUploadServlet in the Administration service in Novell GroupWise 2014 before SP1 allows remote attackers to read or write to arbitrary files via the poLibMaintenanceFileSave parameter, aka ZDI-CAN-2287.
Published: 2014-08-29 IBM Worklight Foundation 5.x and 6.x before 184.108.40.206, as used in Worklight and Mobile Foundation, allows remote authenticated users to bypass the application-authenticity feature via unspecified vectors.
Published: 2014-08-29 The Configuration Patterns component in IBM Flex System Manager (FSM) 1.2.0.x, 1.2.1.x, 1.3.0.x, and 1.3.1.x uses a weak algorithm in an encryption step during Chassis Management Module (CMM) account creation, which makes it easier for remote authenticated users to defeat cryptographic protection me...
Published: 2014-08-29 Cross-site request forgery (CSRF) vulnerability in IBM Maximo Asset Management 7.1 through 220.127.116.11 and 7.5 through 18.104.22.168 and Maximo Asset Management 7.5.0 through 22.214.171.124 and 7.5.1 through 126.96.36.199 for SmartCloud Control Desk allows remote authenticated users to hijack the authentication of arbitr...
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.