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.
                
            Metrics
Affected Vendors & Products
Advisories
    | Source | ID | Title | 
|---|---|---|
  Debian DLA | 
                DLA-3564-1 | e2guardian security update | 
  EUVD | 
                EUVD-2021-31119 | 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. | 
Fixes
    Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
        History
                    No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T04:17:24.889Z
Reserved: 2021-11-29T00:00:00
Link: CVE-2021-44273
No data.
Status : Modified
Published: 2021-12-23T12:15:07.387
Modified: 2024-11-21T06:30:41.833
Link: CVE-2021-44273
No data.
                        OpenCVE Enrichment
                    No data.
 Debian DLA
 EUVD