This page was not yet optimized for use on mobile devices.
CVE-2017-9527
Data ?
Vulnerability ID | CVE-2017-9527 |
---|---|
Published on | 11.06.2017 17:29 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:mruby:mruby:-:*:*:*:*:*:*:*, cpe:2.3:a:mruby:mruby:-:*:*:*:*:ruby:*:*, cpe:2.3:a:mruby:mruby:1.0.0:*:*:*:*:*:*:*, cpe:2.3:a:mruby:mruby:1.0.0:*:*:*:*:ruby:*:*, cpe:2.3:a:mruby:mruby:1.1.0:*:*:*:*:*:*:*, cpe:2.3:a:mruby:mruby:1.1.0:*:*:*:*:ruby:*:*, cpe:2.3:a:mruby:mruby:1.2.0:*:*:*:*:*:*:*, cpe:2.3:a:mruby:mruby:1.2.0:*:*:*:*:ruby:*:*
- cpe:2.3:o:debian:debian_linux:9.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.