This page was not yet optimized for use on mobile devices.
CVE-2018-3740
Data ?
Vulnerability ID | CVE-2018-3740 |
---|---|
Published on | 30.03.2018 19:29 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:sanitize_project:sanitize:1.0.0:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.1:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.2:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.3:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.4:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.5:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.6:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.7:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.0.8:*:*:*:*:ruby:*:*,
cpe:2.3:a:sanitize_project:sanitize:1.1.0:*:*:*:*: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.