This page was not yet optimized for use on mobile devices.
CVE-2018-16468
Data ?
Vulnerability ID | CVE-2018-16468 |
---|---|
Published on | 30.10.2018 21:29 |
Severity | MEDIUM |
Vulnerable configurations ?
-
cpe:2.3:a:loofah_project:loofah:0.2.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.2.1:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.2.2:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.3.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.3.1:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.4.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.4.1:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.4.2:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.4.3:*:*:*:*:ruby:*:*,
cpe:2.3:a:loofah_project:loofah:0.4.4:*:*:*:*: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.