This page was not yet optimized for use on mobile devices.
CVE-2021-3842
Data ?
Vulnerability ID | CVE-2021-3842 |
---|---|
Published on | 04.01.2022 15:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:nltk:nltk:2.0.1:rc1:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:2.0.1:rc2:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:2.0.1:rc3:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:2.0.1:rc4:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:2.0.3:*:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:2.0.4:*:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:3.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:3.0.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:3.0.0:alpha4:*:*:*:*:*:*,
cpe:2.3:a:nltk:nltk:3.0.0:beta1:*:*:*:*:*:*,
…
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.