Red Hat JBoss Core Services Apache HTTP Server 2.4.37 Service Pack 2 Release Notes

Red Hat JBoss Core Services 2.4.37

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

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.37.

Preface

Welcome to the Red Hat JBoss Core Services version 2.4.37 Service Pack 2 release.

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.37

The Apache HTTP Server 2.4.37 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.37

Note

Where a Red Hat JBoss Core Services Apache HTTP Server 2.4.29 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.37 Service Pack 2 requires:

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

Prerequisites

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

Procedure

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

  1. Shutdown any running instances of Red Hat JBoss Core Services Apache HTTP Server 2.4.29.
  2. Backup the Red Hat JBoss Core Services Apache HTTP Server 2.4.29 installation and configuration files.
  3. Install the Red Hat JBoss Core Services Apache HTTP Server 2.4.37 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.29 to version 2.4.37.

    Note

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

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

Additional Resources

Chapter 3. Security Fixes

This update includes fixes for the following security related issues:

IDImpactSummary

CVE-2019-1547

Moderate

openssl: side-channel weak encryption vulnerability

CVE-2019-1549

Low

openssl: information disclosure in fork()

CVE-2019-1563

Low

openssl: information disclosure in PKCS7_dataDecode and CMS_decrypt_set1_pkey

CVE-2019-10081

Moderate

httpd: memory corruption on early pushes

CVE-2019-10082

Moderate

httpd: read-after-free in h2 connection shutdown

CVE-2019-10092

Low

httpd: limited cross-site scripting in mod_proxy error page

CVE-2019-10097

Moderate

httpd: null-pointer dereference in mod_remoteip

CVE-2019-10098

Low

httpd: mod_rewrite potential open redirect

CVE-2020-1927

Moderate

httpd: mod_rewrite configurations vulnerable to open redirect

Chapter 4. Resolved issues

The following are resolved issues for this release:

IssueSummary

JBCS-854

mod_cluster + mod_proxy_wstunnel doesn’t work - all workers are in an error state

JBCS-855

[DOC bug] no Descriptions in the patch detail page

JBCS-879

Windows postinstall fails on Windows Server 2019

JBCS-880

increase postinstall’s verbosity

JBCS-930

support secret="secret" in AJP nodes

Chapter 5. Known issues

The following are known issues for this release:

IssueSummary

JBCS-854

mod_cluster + mod_proxy_wstunnel doesn’t work - all workers are in an error state

JBCS-924

Missing openssl.cnf

Chapter 6. Upgraded components

This release does not include any upgraded components.

Legal Notice

Copyright © 2022 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.