hhund
commented
1 year ago Hi @christiangierschner,
thank you for the report. Here is our assessment on the issues closed with Apache 2.4.55:
moderate: mod_dav out of bounds read, or write of zero byte (CVE-2006-20001) A carefully crafted If: request header can cause a memory read, or write of a single zero byte, in a pool (heap) memory location beyond the header value sent. This could cause the process to crash.
CVE-2006-20001 is not relevant for DSF FHIR Proxy Version 0.9.0 since mod_dav is not being used.
moderate: Apache HTTP Server: mod_proxy_ajp Possible request smuggling (CVE-2022-36760) Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in mod_proxy_ajp of Apache HTTP Server allows an attacker to smuggle requests to the AJP server it forwards requests to. This issue affects Apache HTTP Server Apache HTTP Server 2.4 version 2.4.54 and prior versions.
CVE-2022-36760 is not relevant for DSF FHIR Proxy Version 0.9.0 since mod_proxy_ajp is not being used.
moderate: Apache HTTP Server: mod_proxy prior to 2.4.55 allows a backend to trigger HTTP response splitting (CVE-2022-37436) Prior to Apache HTTP Server 2.4.55, a malicious backend can cause the response headers to be truncated early, resulting in some headers being incorporated into the response body. If the later headers have any security purpose, they will not be interpreted by the client.
CVE-2022-37436 is not relevant for DSF FHIR Proxy Version 0.9.0. The module mod_proxy is being used, but the DSF FHIR Server Version 0.9.0 is not a malicious backend and we are not sending any response headers with security purpose.
Based on this assessment there is no need to publish a new version before the next scheduled release.
schwzr
Hi,
our scan revealed, that the dsf fhir-proxy uses a vulnerable apache version...
According to the changelog of the new 2.4.55, this affects the modules mod_proxy and mod_proxy_ajp...is this used in the fhir-proxy?
https://httpd.apache.org/security/vulnerabilities_24.html