e2guardian v5.4.x <= v5.4.3r is affected by missing SSL...
High severity
Unreviewed
Published
Dec 24, 2021
to the GitHub Advisory Database
•
Updated Sep 13, 2023
Description
Published by the National Vulnerability Database
Dec 23, 2021
Published to the GitHub Advisory Database
Dec 24, 2021
Last updated
Sep 13, 2023
e2guardian v5.4.x <= v5.4.3r is affected by missing SSL certificate validation in the SSL MITM engine. In standalone mode (i.e., acting as a proxy or a transparent proxy), with SSL MITM enabled, e2guardian, if built with OpenSSL v1.1.x, did not validate hostnames in certificates of the web servers that it connected to, and thus was itself vulnerable to MITM attacks.
References