Atomicorp WAF Rule 390616

Rule Summary

• Rule ID: 390616
• Status: Active
• Alert message: Atomicorp.com WAF Rules: POST request must have a Content-Length header
• Observed CWEs: CWE-918 (1)
• Revision: 4
• Rule severity: Warning (4)
• Phase: 2 (request body)
• Rule action: deny
• HTTP status: 403
• Logging: log, auditlog

Description

This rule detects to see if a POST request has a Content-Length header. Per the RFC, a valid Content-Length is required on all HTTP POST requests.

False Positives

No known false positives. If you see this behavior it is caused by either a buggy, non-compliant application, or it may be part of an attack.

It is not recommended that you disable this rule if you have a false positive. If you believe this is a false positive, please report this to our security team to determine if this is a legitimate case, or if its clever attack on your system. Instructions to report false positives are detailed on the Reporting False Positives wiki page. If it is a false positive, we will fix the issue in the rules and get a release out to you promptly.

Tuning Guidance

If you know that this behavior is acceptable for your application, you can disable this rule for that application. Please see the Tuning the Atomicorp WAF Rules page for basic information.

Selected Related CVEs

This is a selected list of documented research observations, not an exhaustive coverage matrix. Absence of a CVE does not imply absence of protection.

Observed CWEs

These CWEs are recorded on published CVEs in the selected observations associated with this rule. They are observational relationships, not a claim that the rule universally blocks every vulnerability assigned to a CWE.

Documentation Source

• Original wiki page: WAF 390616
• Source revision: 2055
• Source revision date: 2012-01-06