This page was not yet optimized for use on mobile devices.
CVE-2018-25022
Data ?
Vulnerability ID | CVE-2018-25022 |
---|---|
Published on | 13.12.2021 01:15 |
Severity | LOW |
Vulnerable configurations ?
-
cpe:2.3:a:toktok:toxcore:0.0.1:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.0.2:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.0.4:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.0.5:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:toktok:toxcore:0.1.4:*:*:*:*:*:*:*,
…
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.