This page was not yet optimized for use on mobile devices.
CVE-2022-32511
Data
| Vulnerability ID | CVE-2022-32511 |
|---|---|
| Published on | 06.06.2022 22:15 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:jmespath_project:jmespath:-:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:0.2.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:0.9.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.0.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.0.1:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.0.2:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.1.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.1.1:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.1.2:*:*:*:*:ruby:*:*,
cpe:2.3:a:jmespath_project:jmespath:1.1.3:*:*:*:*:ruby:*:*,
…
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.