This page was not yet optimized for use on mobile devices.
CVE-2022-41318
Data ?
Vulnerability ID | CVE-2022-41318 |
---|---|
Published on | 25.12.2022 19:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:squid-cache:squid:2.5:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable1:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable2:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable3:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable4:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable5:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable6:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable7:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable8:*:*:*:*:*:*:*,
cpe:2.3:a:squid-cache:squid:2.5.stable9:*:*:*:*:*:*:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.