This page was not yet optimized for use on mobile devices.
CVE-2016-3191
Data
| Vulnerability ID | CVE-2016-3191 |
|---|---|
| Published on | 17.03.2016 23:59 |
| Severity | CRITICAL |
Vulnerable configurations
- cpe:2.3:a:pcre:pcre2:-:*:*:*:*:*:*:*, cpe:2.3:a:pcre:pcre2:10.00:*:*:*:*:*:*:*, cpe:2.3:a:pcre:pcre2:10.10:*:*:*:*:*:*:*, cpe:2.3:a:pcre:pcre2:10.20:*:*:*:*:*:*:*, cpe:2.3:a:pcre:pcre2:10.21:*:*:*:*:*:*:*
- cpe:2.3:a:pcre:pcre:8.00:*:*:*:*:*:*:*
- cpe:2.3:a:pcre:pcre:8.01:*:*:*:*:*:*:*
- cpe:2.3:a:pcre:pcre:8.02:*:*:*:*:*:*:*
- cpe:2.3:a:pcre:pcre:8.10:*:*:*:*:*:*:*
- cpe:2.3:a:pcre:pcre:8.11:*:*:*:*:*:*:*
-
…
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.