This page was not yet optimized for use on mobile devices.
CVE-2022-39177
Data ?
Vulnerability ID | CVE-2022-39177 |
---|---|
Published on | 02.09.2022 04:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:bluez:bluez:-:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.0:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.1:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.2:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.3:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.4:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.5:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.6:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.7:*:*:*:*:*:*:*,
cpe:2.3:a:bluez:bluez:4.8:*:*:*:*:*:*:*,
…
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.