ID CVE-2019-0197
Summary A vulnerability was found in Apache HTTP Server 2.4.34 to 2.4.38. When HTTP/2 was enabled for a http: host or H2Upgrade was enabled for h2 on a https: host, an Upgrade request from http/1.1 to http/2 that was not the first request on a connection could lead to a misconfiguration and crash. Server that never enabled the h2 protocol or that only enabled it for https: and did not set "H2Upgrade on" are unaffected by this issue.
References
Vulnerable Configurations
  • Apache Software Foundation Apache HTTP Server 2.4.17
    cpe:2.3:a:apache:http_server:2.4.17
  • Apache Software Foundation Apache HTTP Server 2.4.18
    cpe:2.3:a:apache:http_server:2.4.18
  • Apache Software Foundation HTTP Server 2.4.19
    cpe:2.3:a:apache:http_server:2.4.19
  • Apache Software Foundation HTTP Server 2.4.20
    cpe:2.3:a:apache:http_server:2.4.20
  • Apache Software Foundation Apache HTTP Server 2.4.21
    cpe:2.3:a:apache:http_server:2.4.21
  • Apache Software Foundation Apache HTTP Server 2.4.22
    cpe:2.3:a:apache:http_server:2.4.22
  • Apache Software Foundation HTTP Server 2.4.23
    cpe:2.3:a:apache:http_server:2.4.23
  • Apache Software Foundation HTTP Server 2.4.24
    cpe:2.3:a:apache:http_server:2.4.24
  • Apache Software Foundation Apache HTTP Server 2.4.25
    cpe:2.3:a:apache:http_server:2.4.25
  • Apache Software Foundation Apache HTTP Server 2.4.26
    cpe:2.3:a:apache:http_server:2.4.26
  • Apache Software Foundation Apache HTTP Server 2.4.27
    cpe:2.3:a:apache:http_server:2.4.27
  • Apache Software Foundation Apache HTTP Server 2.4.28
    cpe:2.3:a:apache:http_server:2.4.28
  • Apache Software Foundation Apache HTTP Server 2.4.29
    cpe:2.3:a:apache:http_server:2.4.29
  • Apache Software Foundation HTTP Server 2.4.30
    cpe:2.3:a:apache:http_server:2.4.30
  • Apache Software Foundation Apache HTTP Server 2.4.32
    cpe:2.3:a:apache:http_server:2.4.32
  • Apache Software Foundation Apache HTTP Server 2.4.33
    cpe:2.3:a:apache:http_server:2.4.33
  • Apache Software Foundation HTTP Server 2.4.34
    cpe:2.3:a:apache:http_server:2.4.34
  • Apache Software Foundation HTTP Server 2.4.35
    cpe:2.3:a:apache:http_server:2.4.35
  • Apache Software Foundation HTTP Server 2.4.36
    cpe:2.3:a:apache:http_server:2.4.36
  • Apache Software Foundation HTTP Server 2.4.37
    cpe:2.3:a:apache:http_server:2.4.37
  • Apache Software Foundation HTTP Server 2.4.38
    cpe:2.3:a:apache:http_server:2.4.38
CVSS
Base: 4.9
Impact:
Exploitability:
CWE CWE-444
CAPEC
  • HTTP Request Splitting
    HTTP Request Splitting (also known as HTTP Request Smuggling) is an attack pattern where an attacker attempts to insert additional HTTP requests in the body of the original (enveloping) HTTP request in such a way that the browser interprets it as one request but the web server interprets it as two. There are several ways to perform HTTP request splitting attacks. One way is to include double Content-Length headers in the request to exploit the fact that the devices parsing the request may each use a different header. Another way is to submit an HTTP request with a "Transfer Encoding: chunked" in the request header set with setRequestHeader to allow a payload in the HTTP Request that can be considered as another HTTP Request by a subsequent parsing entity. A third way is to use the "Double CR in an HTTP header" technique. There are also a few less general techniques targeting specific parsing vulnerabilities in certain web servers.
  • HTTP Request Smuggling
    HTTP Request Smuggling results from the discrepancies in parsing HTTP requests between HTTP entities such as web caching proxies or application firewalls. Entities such as web servers, web caching proxies, application firewalls or simple proxies often parse HTTP requests in slightly different ways. Under specific situations where there are two or more such entities in the path of the HTTP request, a specially crafted request is seen by two attacked entities as two different sets of requests. This allows certain requests to be smuggled through to a second entity without the first one realizing it.
Last major update 11-06-2019 - 18:29
Published 11-06-2019 - 18:29
Last modified 17-06-2019 - 15:15
Back to Top