CVE-2007-6203
Last modified
CVE-2007-6203 is a vulnerability of currently unknown severity. Apache HTTP Server 2.0.x and 2.2.x does not sanitize the HTTP Method specifier header from an HTTP request when it is reflected back in a "413 Request Entity Too Large" error message, which might allow cross-site scripting (XSS) style attacks using web client components that can send arbitrary headers in requests, as demonstrated via an HTTP request containing an invalid Content-length value, a similar issue to CVE-2006-3918.. EPSS estimates a 80.75% chance of exploitation in the next 30 days.
Description
Apache HTTP Server 2.0.x and 2.2.x does not sanitize the HTTP Method specifier header from an HTTP request when it is reflected back in a "413 Request Entity Too Large" error message, which might allow cross-site scripting (XSS) style attacks using web client components that can send arbitrary headers in requests, as demonstrated via an HTTP request containing an invalid Content-length value, a similar issue to CVE-2006-3918.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Http Server | 2.0.46 |
| Apache | Http Server | 2.0.47 |
| Apache | Http Server | 2.0.48 |
| Apache | Http Server | 2.0.49 |
| Apache | Http Server | 2.0.50 |
| Apache | Http Server | 2.0.51 |
| Apache | Http Server | 2.0.52 |
| Apache | Http Server | 2.0.53 |
| Apache | Http Server | 2.0.54 |
| Apache | Http Server | 2.0.55 |
| Apache | Http Server | 2.0.57 |
| Apache | Http Server | 2.0.58 |
| Apache | Http Server | 2.0.59 |
| Apache | Http Server | 2.1.1 |
| Apache | Http Server | 2.1.2 |
| Apache | Http Server | 2.1.3 |
| Apache | Http Server | 2.1.4 |
| Apache | Http Server | 2.1.5 |
| Apache | Http Server | 2.1.6 |
| Apache | Http Server | 2.1.7 |
| Apache | Http Server | 2.1.8 |
| Apache | Http Server | 2.2.0 |
| Apache | Http Server | 2.2.2 |
| Apache | Http Server | 2.2.3 |
| Apache | Http Server | 2.2.4 |
References
- http://secunia.com/advisories/27906Vendor Advisory
- http://secunia.com/advisories/28196Vendor Advisory
- http://secunia.com/advisories/29348Vendor Advisory
- http://secunia.com/advisories/29420Vendor Advisory
- http://secunia.com/advisories/29640Vendor Advisory
- http://secunia.com/advisories/30356Vendor Advisory
- http://secunia.com/advisories/30732Vendor Advisory
- http://secunia.com/advisories/33105Vendor Advisory
- http://secunia.com/advisories/34219Vendor Advisory
- http://secunia.com/advisories/27906Vendor Advisory
- http://secunia.com/advisories/28196Vendor Advisory
- http://secunia.com/advisories/29348Vendor Advisory
- http://secunia.com/advisories/29420Vendor Advisory
- http://secunia.com/advisories/29640Vendor Advisory
- http://secunia.com/advisories/30356Vendor Advisory
- http://secunia.com/advisories/30732Vendor Advisory
- http://secunia.com/advisories/33105Vendor Advisory
- http://secunia.com/advisories/34219Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2007-6203?
How severe is CVE-2007-6203?
How do I fix CVE-2007-6203?
Are you affected by CVE-2007-6203?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
