Signature Detail

HTTP: Invalid Request Format

This protocol anomaly triggers when it detects an invalid HTTP request format, such as a request that begins before a previous one ends.

Extended Description

An HTTP request message that does not follow the RFC specifications, for example, having a request header beginning before another one ends, constitutes a protocol anomaly. An attacker could forge an HTTP message, causing some implementations to improperly handle the packet, resulting in a denial of service, buffer overflow, or information disclosure.

References

• URL: http://www.faqs.org/rfcs/rfc2616.html