Potential SSRF in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to cause unsafe RewriteRules to unexpectedly setup URLs to be handled by mod_proxy.
Users are recommended to upgrade to version 2.4.60, which fixes this issue.
Weakness
The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Http_server |
Apache |
2.4.0 (including) |
2.4.60 (excluding) |
| JBoss Core Services for RHEL 8 |
RedHat |
jbcs-httpd24-httpd-0:2.4.57-13.el8jbcs |
* |
| JBoss Core Services for RHEL 8 |
RedHat |
jbcs-httpd24-mod_http2-0:1.15.19-41.el8jbcs |
* |
| JBoss Core Services for RHEL 8 |
RedHat |
jbcs-httpd24-mod_jk-0:1.2.49-11.redhat_1.el8jbcs |
* |
| JBoss Core Services for RHEL 8 |
RedHat |
jbcs-httpd24-mod_md-1:2.4.24-11.el8jbcs |
* |
| JBoss Core Services for RHEL 8 |
RedHat |
jbcs-httpd24-mod_proxy_cluster-0:1.3.20-8.el8jbcs |
* |
| JBoss Core Services for RHEL 8 |
RedHat |
jbcs-httpd24-mod_security-0:2.9.3-40.el8jbcs |
* |
| JBoss Core Services on RHEL 7 |
RedHat |
jbcs-httpd24-httpd-0:2.4.57-13.el7jbcs |
* |
| JBoss Core Services on RHEL 7 |
RedHat |
jbcs-httpd24-mod_http2-0:1.15.19-41.el7jbcs |
* |
| JBoss Core Services on RHEL 7 |
RedHat |
jbcs-httpd24-mod_jk-0:1.2.49-11.redhat_1.el7jbcs |
* |
| JBoss Core Services on RHEL 7 |
RedHat |
jbcs-httpd24-mod_md-1:2.4.24-11.el7jbcs |
* |
| JBoss Core Services on RHEL 7 |
RedHat |
jbcs-httpd24-mod_proxy_cluster-0:1.3.20-8.el7jbcs |
* |
| JBoss Core Services on RHEL 7 |
RedHat |
jbcs-httpd24-mod_security-0:2.9.3-40.el7jbcs |
* |
| Red Hat Enterprise Linux 8 |
RedHat |
httpd:2.4-8100020240712114234.489197e6 |
* |
| Red Hat Enterprise Linux 9 |
RedHat |
httpd-0:2.4.57-11.el9_4 |
* |
| Red Hat Enterprise Linux 9.2 Extended Update Support |
RedHat |
httpd-0:2.4.53-11.el9_2.10 |
* |
| Text-Only JBCS |
RedHat |
jbcs-httpd24-httpd |
* |
| Apache2 |
Ubuntu |
devel |
* |
| Apache2 |
Ubuntu |
esm-infra/focal |
* |
| Apache2 |
Ubuntu |
focal |
* |
| Apache2 |
Ubuntu |
jammy |
* |
| Apache2 |
Ubuntu |
mantic |
* |
| Apache2 |
Ubuntu |
noble |
* |
| Apache2 |
Ubuntu |
oracular |
* |
| Apache2 |
Ubuntu |
plucky |
* |
| Apache2 |
Ubuntu |
trusty/esm |
* |
| Apache2 |
Ubuntu |
upstream |
* |
Extended Description
Input validation is a frequently-used technique
for checking potentially dangerous inputs in order to
ensure that the inputs are safe for processing within the
code, or when communicating with other components.
Input can consist of:
Data can be simple or structured. Structured data
can be composed of many nested layers, composed of
combinations of metadata and raw data, with other simple or
structured data.
Many properties of raw data or metadata may need
to be validated upon entry into the code, such
as:
Implied or derived properties of data must often
be calculated or inferred by the code itself. Errors in
deriving properties may be considered a contributing factor
to improper input validation.
Potential Mitigations
- 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.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.
- Inputs should be decoded and canonicalized to the application’s current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control.
- Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.
References