E2Guardian
Approved changes feed: RSS · Atom
cpe:2.3:a:e2bn:e2guardian:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | E2Bn (e18efc7c-fbc3-5f80-9f9a-ae76f035b63a) |
|---|---|
| Product | E2Guardian (8aab21ca-e72e-5713-98b1-0f118925219a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/e2guardian/e2guardian |
purl2cpe | 2026-06-01 10:12:06.199135 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-44273 |
vulnerable | 2026-06-08 05:36:45.645024 |
Details available
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.
Published: 2021-12-23T00:00:00.000Z
Updated: 2024-08-04T04:17:24.889Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.