CVE-2019-0197: Medium severity Apache HTTP Server vulnerability

Published Feb 1, 2019
·
Updated

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.

Other sources

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. A server that never enabled the h2 protocol or that only enabled it for https: and did not configure the "H2Upgrade on" is unaffected by this.

— Red Hat

Affected Software

53 affected componentsFixes available
redhat/jbcs-httpd24-apr<0:1.6.3-63.jbcs.el6
0:1.6.3-63.jbcs.el6
redhat/jbcs-httpd24-apr-util<0:1.6.1-48.jbcs.el6
0:1.6.1-48.jbcs.el6
redhat/jbcs-httpd24-brotli<0:1.0.6-7.jbcs.el6
0:1.0.6-7.jbcs.el6
redhat/jbcs-httpd24-curl<0:7.64.1-14.jbcs.el6
0:7.64.1-14.jbcs.el6
redhat/jbcs-httpd24-httpd<0:2.4.37-33.jbcs.el6
0:2.4.37-33.jbcs.el6
redhat/jbcs-httpd24-jansson<0:2.11-20.jbcs.el6
0:2.11-20.jbcs.el6
redhat/jbcs-httpd24-nghttp2<0:1.39.2-4.jbcs.el6
0:1.39.2-4.jbcs.el6
redhat/jbcs-httpd24-openssl<1:1.1.1-25.jbcs.el6
1:1.1.1-25.jbcs.el6
redhat/jbcs-httpd24-curl<0:7.64.1-36.jbcs.el6
0:7.64.1-36.jbcs.el6
redhat/jbcs-httpd24-httpd<0:2.4.37-57.jbcs.el6
0:2.4.37-57.jbcs.el6
redhat/jbcs-httpd24-nghttp2<0:1.39.2-25.jbcs.el6
0:1.39.2-25.jbcs.el6
redhat/jbcs-httpd24-apr<0:1.6.3-63.jbcs.el7
0:1.6.3-63.jbcs.el7
redhat/jbcs-httpd24-apr-util<0:1.6.1-48.jbcs.el7
0:1.6.1-48.jbcs.el7
redhat/jbcs-httpd24-brotli<0:1.0.6-7.jbcs.el7
0:1.0.6-7.jbcs.el7
redhat/jbcs-httpd24-curl<0:7.64.1-14.jbcs.el7
0:7.64.1-14.jbcs.el7
redhat/jbcs-httpd24-httpd<0:2.4.37-33.jbcs.el7
0:2.4.37-33.jbcs.el7
redhat/jbcs-httpd24-jansson<0:2.11-20.jbcs.el7
0:2.11-20.jbcs.el7
redhat/jbcs-httpd24-nghttp2<0:1.39.2-4.jbcs.el7
0:1.39.2-4.jbcs.el7
redhat/jbcs-httpd24-openssl<1:1.1.1-25.jbcs.el7
1:1.1.1-25.jbcs.el7
redhat/jbcs-httpd24-curl<0:7.64.1-36.jbcs.el7
0:7.64.1-36.jbcs.el7
redhat/jbcs-httpd24-httpd<0:2.4.37-57.jbcs.el7
0:2.4.37-57.jbcs.el7
redhat/jbcs-httpd24-nghttp2<0:1.39.2-25.jbcs.el7
0:1.39.2-25.jbcs.el7
redhat/jbcs-httpd24-openssl-pkcs11<0:0.4.10-7.jbcs.el7
0:0.4.10-7.jbcs.el7
Apache HTTP Server>=2.4.34<=2.4.38
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.04
Fedoraproject Fedora=30
openSUSE Leap=15.0
openSUSE Leap=42.3
All of the following
redhat JBoss Core Services=1.0
Any of the following
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
Oracle Communications Session Report Manager=8.0.0
Oracle Communications Session Report Manager=8.1.0
Oracle Communications Session Report Manager=8.1.1
Oracle Communications Session Report Manager=8.2.0
Oracle Communications Session Route Manager=8.0.0
Oracle Communications Session Route Manager=8.1.0
Oracle Communications Session Route Manager=8.1.1
Oracle Communications Session Route Manager=8.2.0
Oracle Enterprise Manager Ops Center=12.3.3
Oracle Enterprise Manager Ops Center=12.4.0
Oracle HTTP Server=12.2.1.3.0
Oracle Instantis Enterprisetrack=17.1
Oracle Instantis Enterprisetrack=17.2
Oracle Instantis Enterprisetrack=17.3
Oracle Retail Xstore Point of Service=7.0
Oracle Retail Xstore Point of Service=7.1
redhat JBoss Core Services=1.0
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
debian/apache2
2.4.62-1~deb11u12.4.66-1~deb11u12.4.66-1~deb12u12.4.62-1~deb12u22.4.66-1~deb13u22.4.66-8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jbcs-httpd24-apr to a version that resolves this vulnerability.

    Fixed in 0:1.6.3-63.jbcs.el6
  2. Upgrade

    Upgrade redhat/jbcs-httpd24-apr-util to a version that resolves this vulnerability.

    Fixed in 0:1.6.1-48.jbcs.el6
  3. Upgrade

    Upgrade redhat/jbcs-httpd24-brotli to a version that resolves this vulnerability.

    Fixed in 0:1.0.6-7.jbcs.el6
  4. Upgrade

    Upgrade redhat/jbcs-httpd24-curl to a version that resolves this vulnerability.

    Fixed in 0:7.64.1-14.jbcs.el6
  5. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-33.jbcs.el6
  6. Upgrade

    Upgrade redhat/jbcs-httpd24-jansson to a version that resolves this vulnerability.

    Fixed in 0:2.11-20.jbcs.el6
  7. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-4.jbcs.el6
  8. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1-25.jbcs.el6
  9. Upgrade

    Upgrade redhat/jbcs-httpd24-curl to a version that resolves this vulnerability.

    Fixed in 0:7.64.1-36.jbcs.el6
  10. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-57.jbcs.el6
  11. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-25.jbcs.el6
  12. Upgrade

    Upgrade redhat/jbcs-httpd24-apr to a version that resolves this vulnerability.

    Fixed in 0:1.6.3-63.jbcs.el7
  13. Upgrade

    Upgrade redhat/jbcs-httpd24-apr-util to a version that resolves this vulnerability.

    Fixed in 0:1.6.1-48.jbcs.el7
  14. Upgrade

    Upgrade redhat/jbcs-httpd24-brotli to a version that resolves this vulnerability.

    Fixed in 0:1.0.6-7.jbcs.el7
  15. Upgrade

    Upgrade redhat/jbcs-httpd24-curl to a version that resolves this vulnerability.

    Fixed in 0:7.64.1-14.jbcs.el7
  16. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-33.jbcs.el7
  17. Upgrade

    Upgrade redhat/jbcs-httpd24-jansson to a version that resolves this vulnerability.

    Fixed in 0:2.11-20.jbcs.el7
  18. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-4.jbcs.el7
  19. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1-25.jbcs.el7
  20. Upgrade

    Upgrade redhat/jbcs-httpd24-curl to a version that resolves this vulnerability.

    Fixed in 0:7.64.1-36.jbcs.el7
  21. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-57.jbcs.el7
  22. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-25.jbcs.el7
  23. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl-pkcs11 to a version that resolves this vulnerability.

    Fixed in 0:0.4.10-7.jbcs.el7
  24. Upgrade

    Upgrade debian/apache2 to a version that resolves this vulnerability.

    Fixed in 2.4.62-1~deb11u1Fixed in 2.4.66-1~deb11u1Fixed in 2.4.66-1~deb12u1Fixed in 2.4.62-1~deb12u2Fixed in 2.4.66-1~deb13u2Fixed in 2.4.66-8
  25. Configuration

    Configure HTTP/2 so it is not enabled for http: hosts, and do not set "H2Upgrade on" for https: hosts.

    Apache HTTP Server h2 protocol and H2Upgrade = Enable h2 only for https: hosts; do not set H2Upgrade on

Event History

Feb 1, 2019
CVE Published
12:00 AM
Apr 2, 2019
Data Sourced
via Red Hat·11:18 AM
DescriptionSeverityAffected Software
Jun 11, 2019
CVE Published
via MITRE·09:35 PM
Data Sourced
via MITRE·09:35 PM
DescriptionWeakness
Event
via NVD·10:29 PM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2019-0197?

The severity of CVE-2019-0197 is rated as high due to its potential to cause server crashes.

2

How do I fix CVE-2019-0197?

To fix CVE-2019-0197, upgrade your Apache HTTP Server to version 2.4.39 or later.

3

Which versions of Apache HTTP Server are affected by CVE-2019-0197?

CVE-2019-0197 affects Apache HTTP Server versions 2.4.34 to 2.4.38.

4

What types of systems are vulnerable to CVE-2019-0197?

Systems running Apache HTTP Server with HTTP/2 protocol enabled are vulnerable to CVE-2019-0197.

5

Is there a workaround for CVE-2019-0197 if immediate patching is not possible?

Disabling the HTTP/2 protocol or H2Upgrade can serve as a temporary workaround for CVE-2019-0197.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203