Red Hat JBoss Core Services Apache HTTP Server 2.4.29 Service Pack 3 Release Notes

Red Hat JBoss Core Services 2.4.29

For Use with the Red Hat JBoss Core Services Apache HTTP Server 2.4.29

Red Hat Customer Content Services

Abstract

These release notes contain important information related to the Red Hat JBoss Core Services Apache HTTP Server 2.4.29.

Preface

Welcome to the Red Hat JBoss Core Services version 2.4.29 Service Pack 3 release.

The purpose of release 2.4.29 Service Pack 3 is to cover an important security issue impacting JBCS 2.4.29.

Important

This service pack for Red Hat JBoss Core Services Apache HTTP Server does NOT support Solaris.

Red Hat JBoss Core Services Apache HTTP Server is an open source web server developed by the Apache Software Foundation. Features of Apache HTTP Server include:

  • Implements the current HTTP standards, including HTTP/1.1 and HTTP/2.
  • Transport Layer Security (TLS) encryption support though OpenSSL, providing secure connections between the web server and web clients.
  • Extendable though modules, some of which are included with the Red Hat JBoss Core Services Apache HTTP Server.

Chapter 1. Installing the Red Hat JBoss Core Services 2.4.29 Service Pack 3

The Apache HTTP Server 2.4.29 Service Pack 3 can be installed using one of the following sections of the installation guide:

Chapter 2. Upgrading to the Red Hat JBoss Core Services Apache HTTP Server 2.4.29

Note

Where a Red Hat JBoss Core Services Apache HTTP Server 2.4.23 or earlier was installed from RPMs packages using yum, the Apache HTTP Server can be upgraded with yum upgrade.

For systems where an earlier version of the Red Hat JBoss Core Services Apache HTTP Server was installed from a .zip archive, upgrading to the Apache HTTP Server 2.4.29 Service Pack 3 requires:

  1. Installing the Apache HTTP Server 2.4.29.
  2. Setting up the Apache HTTP Server 2.4.29.
  3. Removing the earlier version of Apache HTTP Server.

Prerequisites

  • Root user access (Red Hat Enterprise Linux)
  • Administrative access (Windows Server)
  • A system where the Red Hat JBoss Core Services Apache HTTP Server 2.4.23 or earlier was installed from a .zip archive.

Procedure

For systems using the Red Hat JBoss Core Services Apache HTTP Server 2.4.23, the recommended procedure for upgrading to the Apache HTTP Server 2.4.29 is:

  1. Shutdown any running instances of Red Hat JBoss Core Services Apache HTTP Server 2.4.23.
  2. Backup the Red Hat JBoss Core Services Apache HTTP Server 2.4.23 installation and configuration files.
  3. Install the Red Hat JBoss Core Services Apache HTTP Server 2.4.29 using the .zip installation method for the current system (see Additional Resources below).

  4. Migrate your configuration from the Red Hat JBoss Core Services Apache HTTP Server version 2.4.23 to version 2.4.29.

    Note

    The Apache HTTP Server configuration files may have changed since the Apache HTTP Server 2.4.23 release. It is recommended that you update the 2.4.29 version configuration files, rather than overwrite them with the configuration files from a different version (such as Apache HTTP Server 2.4.23).

  5. Remove the Red Hat JBoss Core Services Apache HTTP Server 2.4.23 root directory.

Additional Resources

Chapter 3. Security Fixes

This update includes fixes for the following security related issues:

IDImpactSummary

CVE-2019-9511

Important

HTTP/2: large amount of data requests leads to denial of service

CVE-2019-9513

Important

HTTP/2: flood using PRIORITY frames resulting in excessive resource consumption

CVE-2019-9516

Important

HTTP/2: 0-length headers lead to denial of service

CVE-2019-9517

Important

HTTP/2: request for large response leads to denial of service

Chapter 4. Resolved issues

The following are non-security issues resolved during this release:

IssueDescription

JBCS-806

CVE-2019-9513 nghttp2: HTTP/2: flood using PRIORITY frames resulting in excessive resource consumption [jbcs-httpd-2.4.29-sp2-native]

JBCS-820

CVE-2019-9511 nghttp2: HTTP/2: large amount of data request leads to denial of service [jbcs-httpd-2.4.29-sp2-native]

JBCS-822

CVE-2019-9517 mod_http2: HTTP/2: request for large response leads to denial of service [jbcs-httpd-2.4.29-sp2-native]

JBCS-824

CVE-2019-9516 mod_http2: HTTP/2: 0-length headers leads to denial of service [jbcs-httpd-2.4.29-sp2-native]

JBCS-828

Rebase nghttp2 to 1.39.2

Chapter 5. Known issues

There are currently no known issues for this release

Chapter 6. Upgraded components

The components upgraded in this release are as follows:

JBCS ComponentVersionOperating System

nghttp2

1.39.2

All

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.