CVE-2024-24795

Public on

Last Modified: UTC

Description

A flaw was found in httpd. An HTTP response splitting in multiple httpd modules may allow an attacker that can inject malicious response headers into backend applications to cause an HTTP desynchronization attack.

A flaw was found in httpd. An HTTP response splitting in multiple httpd modules may allow an attacker that can inject malicious response headers into backend applications to cause an HTTP desynchronization attack.

Statement

This flaw only affects configurations when at least one of the following modules is loaded and being used: mod_authnz_fcgi, mod_cgi, mod_cgid, mod_proxy_fcgi, mod_proxy_scgi and mod_proxy_uwsgi. Additionally, this flaw is only exploitable by a malicious backend in a reverse proxy configuration or an attack against a backend application that inserts headers. These modules are enabled by default in Red Hat Enterprise Linux 8, 9, and in RHSCL mod_authnz_fcgi is not available in RHEL8 and RHSCL. These modules can be disabled via the configuration file if their functionality is not being used.

This flaw only affects configurations when at least one of the following modules is loaded and being used: mod_authnz_fcgi, mod_cgi, mod_cgid, mod_proxy_fcgi, mod_proxy_scgi and mod_proxy_uwsgi. Additionally, this flaw is only exploitable by a malicious backend in a reverse proxy configuration or an attack against a backend application that inserts headers.

These modules are enabled by default in Red Hat Enterprise Linux 8, 9, and in RHSCL mod_authnz_fcgi is not available in RHEL8 and RHSCL. These modules can be disabled via the configuration file if their functionality is not being used.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Additional information

  • Bugzilla 2273499: httpd: HTTP Response Splitting in multiple modules
  • CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
  • FAQ: Frequently asked questions about CVE-2024-24795

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown
Red HatNVD

CVSS v3 Base Score

4

N/A

Attack Vector

Network

N/A

Attack Complexity

High

N/A

Privileges Required

None

N/A

User Interaction

None

N/A

Scope

Changed

N/A

Confidentiality Impact

Low

N/A

Integrity Impact

None

N/A

Availability Impact

None

N/A

CVSS v3 Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

Understanding the Weakness (CWE)

CWE-113

Integrity,Access Control

Technical Impact: Modify Application Data; Gain Privileges or Assume Identity

CR and LF characters in an HTTP header may give attackers control of the remaining headers and body of the message that the application intends to send/receive, as well as allowing them to create additional messages entirely under their control.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.