This page was not yet optimized for use on mobile devices.
            
            CVE-2016-3102
Data ?
| Vulnerability ID | CVE-2016-3102 | 
|---|---|
| Published on | 09.02.2017 15:59 | 
| Severity | HIGH | 
Vulnerable configurations ?
- cpe:2.3:a:jenkins:script_security:1.0:*:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:-:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:beta1:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:beta2:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:beta3:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:beta4:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:beta5:*:*:*:jenkins:*:*, cpe:2.3:a:jenkins:script_security:1.0:beta6:*:*:*:jenkins:*:*
 - cpe:2.3:a:jenkins:script_security:1.10:*:*:*:*:jenkins:*:*
 - cpe:2.3:a:jenkins:script_security:1.11:*:*:*:*:jenkins:*:*
 - 
                                            
                                                
… 
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.