Mailing List Archive

svn commit: r1890801 - /httpd/site/trunk/content/security/json/CVE-2021-31618.json
Author: mjc
Date: Tue Jun 15 08:35:50 2021
New Revision: 1890801

URL: http://svn.apache.org/viewvc?rev=1890801&view=rev
Log:
Update to CVE-2021-31618 which after research was found to only affect the unreleased 2.4.47, but did affect
mod_http2 1.15.17 so we won't reject the CVE.

Modified:
httpd/site/trunk/content/security/json/CVE-2021-31618.json

Modified: httpd/site/trunk/content/security/json/CVE-2021-31618.json
URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/security/json/CVE-2021-31618.json?rev=1890801&r1=1890800&r2=1890801&view=diff
==============================================================================
--- httpd/site/trunk/content/security/json/CVE-2021-31618.json (original)
+++ httpd/site/trunk/content/security/json/CVE-2021-31618.json Tue Jun 15 08:35:50 2021
@@ -31,8 +31,8 @@
"version_data": [.
{
"version_name": "",
- "version_affected": "<",
- "version_value": "2.4.48",
+ "version_affected": "=",
+ "version_value": "2.4.47",
"platform": ""
}
]
@@ -59,7 +59,7 @@
"description": {
"description_data": [.
{
- "value": "Apache HTTP Server protocol handler for the HTTP/2 protocol checks received request headers against the size limitations as configured for the server and used for the HTTP/1 protocol as well. On violation of these restrictions and HTTP response is sent to the client with a status code indicating why the request was rejected.\n\nThis rejection response was not fully initialised in the HTTP/2 protocol handler if the offending header was the very first one received or appeared in a a footer. This led to a NULL pointer dereference on initialised memory, crashing reliably the child process. Since such a triggering HTTP/2 request is easy to craft and submit, this can be exploited to DoS the server.\n\nThis affected versions prior to 2.4.48",
+ "value": "Apache HTTP Server protocol handler for the HTTP/2 protocol checks received request headers against the size limitations as configured for the server and used for the HTTP/1 protocol as well. On violation of these restrictions and HTTP response is sent to the client with a status code indicating why the request was rejected.\n\nThis rejection response was not fully initialised in the HTTP/2 protocol handler if the offending header was the very first one received or appeared in a a footer. This led to a NULL pointer dereference on initialised memory, crashing reliably the child process. Since such a triggering HTTP/2 request is easy to craft and submit, this can be exploited to DoS the server.\n\nThis issue affected mod_http2 1.15.17 and Apache HTTP Server version 2.4.47 only. Apache HTTP Server 2.4.47 was never released.",
"lang": "eng"
}
]