This page was not yet optimized for use on mobile devices.
CVE-2022-21699
Data ?
Vulnerability ID | CVE-2022-21699 |
---|---|
Published on | 19.01.2022 22:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:ipython:ipython:2.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:2.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:2.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:2.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:2.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:2.4.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:2.4.1:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:3.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:3.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:ipython:ipython:3.2.0:*:*:*:*:*:*:*,
…
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.