This page was not yet optimized for use on mobile devices.
CVE-2019-11940
Data ?
| Vulnerability ID | CVE-2019-11940 |
|---|---|
| Published on | 04.12.2019 17:16 |
| Severity | CRITICAL |
Vulnerable configurations ?
-
cpe:2.3:a:facebook:proxygen:0.29.0:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:0.30.0:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:0.32.0:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.01.16.00:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.01.23.00:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.01.30.00:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.03.06.00:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.03.13.00:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.03.20.00:*:*:*:*:*:*:*,
cpe:2.3:a:facebook:proxygen:2017.03.27.00:*:*:*:*:*:*:*,
…
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.