Several remotely exploitable request smuggling, memory exhaustion, and HTTP response splitting vulnerabilities have been discovered in the Netty Java NIO client/server socket framework. . These vulnerabilities could result in crashes leading to denial of service (DoS) , the exposure of sensitive information, request smuggling attacks and HTTP response splitting attacks. An important update for Netty that fixes these dangerous bugs has been released. We urge all impacted users to apply the Netty updates issued but their distro(s) now to secure against exploits leading to downtime and compromise. To stay on top of important updates released by the open-source programs and applications you use, be sure to register as a LinuxSecurity user , then subscribe to our Linux Advisory Watch newsletter and customize your advisories for the distro(s) you use. This will enable you to stay up-to-date on the latest, most significant issues impacting the security of your systems. Follow @LS_Advisories on Twitter for real-time updates on advisories for your distro(s) . . Emerging flaws in the Netty framework might result in Denial of Service, leakage of confidential information, and significant security incidents.. Netty Security Update, Request Smuggling, DoS Exploits. . Brittany Day
This technical note describes a detection/prevention technique that works in many cases both with HTTP Response Splitting and with HTTP Request Smuggling. This technique makes use of implicit information found in the TCP stream, namely the segmentation into packets and the TCP PSH bit. In HTTP Response Splitting, the proposed technique needs to be applied at the proxy server, the one closest to the web server, and to the response stream. In HTTP Request Smuggling, this technique needs to be applied at the entity closest to the attacked proxy server/device (i.e. implemented in another proxy server, or the web server itself), and to the request stream (note, however, that this second server may be off the premises of the organization wherein the web server is, see also "Can HTTP Request Smuggling be blocked by Web Application Firewalls?". . The link for this article located at SecuriTeam.com is no longer available. . Discover a method to identify HTTP header manipulation and request forgery by analyzing TCP packet traffic for irregularities and anomalies. HTTP Attack Detection, TCP Response Prevention, Web Security Techniques. . Benjamin D. Thomas
All versions of Apache previous to 2.1.6 are vulnerable to a HTTP request smuggling attack which can allow malicious piggybacking of false HTTP requests hidden within valid content. This method of HTTP Request Smuggling was first discussed by Watchfire some time ago. The issue has been addressed by an update to version 2.1.6. . The vulnerability involves a crafted request with a 'Transfer-Encoding: chunked' header and a 'Content-Length' can cause Apache to forward a modified request with the original 'Content-Length' header. The malicious request may then piggyback with the valid HTTP request possibly resulting in cache poisoning, cross-site scripting, session hijacking and other various kinds of attack. This vulnerability has resurfaced due to vendor confirmation, the original Watchfire Whitepaper on HTTP Request Smuggling is here. addict3d reports that mostly all Apache 2.0.x versions, on the major platforms, are vulnerable to this attack. Apache has promptly released a 2.1.6 version of their HTTP software to address this issue. The link for this article located at Whitedust Security is no longer available. . The vulnerability involves a crafted request with a 'Transfer-Encoding: chunked' header and a 'Conte. versions, apache, previous, vulnerable, request, smuggling, attack, which. . LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.