CVE-2023-31122

Out-of-bounds Read vulnerability in mod_macro of Apache HTTP Server.This issue affects Apache HTTP Server: through 2.4.57.

The product reads data past the end, or before the beginning, of the intended buffer.

Name	Vendor	Start Version	End Version
Http_server	Apache	*	2.4.57 (including)
JBoss Core Services for RHEL 8	RedHat	jbcs-httpd24-httpd-0:2.4.57-9.el8jbcs	*
JBoss Core Services on RHEL 7	RedHat	jbcs-httpd24-httpd-0:2.4.57-9.el7jbcs	*
Red Hat Enterprise Linux 8	RedHat	httpd:2.4-8100020240405103607.e155f54d	*
Red Hat Enterprise Linux 9	RedHat	httpd-0:2.4.57-8.el9	*
Red Hat JBoss Core Services 1	RedHat	httpd	*
Apache2	Ubuntu	bionic	*
Apache2	Ubuntu	devel	*
Apache2	Ubuntu	esm-infra/bionic	*
Apache2	Ubuntu	esm-infra/xenial	*
Apache2	Ubuntu	focal	*
Apache2	Ubuntu	jammy	*
Apache2	Ubuntu	lunar	*
Apache2	Ubuntu	mantic	*
Apache2	Ubuntu	trusty	*
Apache2	Ubuntu	trusty/esm	*
Apache2	Ubuntu	upstream	*
Apache2	Ubuntu	xenial	*

Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2023-31122
CWE	https://cwe.mitre.org/data/definitions/125.html

Out-of-bounds Read