CVE-2016-3102
First published: Thu Feb 09 2017(Updated: )
The Script Security plugin before 1.18.1 in Jenkins might allow remote attackers to bypass a Groovy sandbox protection mechanism via a plugin that performs (1) direct field access or (2) get/set array operations.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Script Security | =1.0 | |
| Jenkins Script Security | =1.1 | |
| Jenkins Script Security | =1.2 | |
| Jenkins Script Security | =1.3 | |
| Jenkins Script Security | =1.4 | |
| Jenkins Script Security | =1.5 | |
| Jenkins Script Security | =1.6 | |
| Jenkins Script Security | =1.7 | |
| Jenkins Script Security | =1.8 | |
| Jenkins Script Security | =1.9 | |
| Jenkins Script Security | =1.10 | |
| Jenkins Script Security | =1.11 | |
| Jenkins Script Security | =1.12 | |
| Jenkins Script Security | =1.13 | |
| Jenkins Script Security | =1.14 | |
| Jenkins Script Security | =1.15 | |
| Jenkins Script Security | =1.16 | |
| Jenkins Script Security | =1.17 | |
| Jenkins Script Security | =1.18 | |
| maven/org.jenkins-ci.plugins:script-security | <1.18.1 | 1.18.1 |
| =1.0 | ||
| =1.1 | ||
| =1.2 | ||
| =1.3 | ||
| =1.4 | ||
| =1.5 | ||
| =1.6 | ||
| =1.7 | ||
| =1.8 | ||
| =1.9 | ||
| =1.10 | ||
| =1.11 | ||
| =1.12 | ||
| =1.13 | ||
| =1.14 | ||
| =1.15 | ||
| =1.16 | ||
| =1.17 | ||
| =1.18 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-3102?
CVE-2016-3102 is classified as a medium severity vulnerability.
How do I fix CVE-2016-3102?
To fix CVE-2016-3102, upgrade the Script Security plugin to version 1.18.1 or later.
Who is affected by CVE-2016-3102?
CVE-2016-3102 affects installations of Jenkins with Script Security plugin versions prior to 1.18.1.
What type of vulnerability is CVE-2016-3102?
CVE-2016-3102 is a sandbox bypass vulnerability that allows attackers to execute unauthorized script operations.
Can CVE-2016-3102 be exploited remotely?
Yes, CVE-2016-3102 can be exploited by remote attackers due to the nature of the sandbox bypass.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/weakness
- agent/description
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-xgjx-96v4-mqxx
- alias/CVE-2016-3102
- agent/software-canonical-lookup
- agent/references
- agent/last-modified-date
- agent/severity
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/nvd-cve
- source/NVD
- collector/github-advisory
- vendor/jenkins
- canonical/jenkins script security
- version/jenkins script security/1.0
- version/jenkins script security/1.1
- version/jenkins script security/1.2
- version/jenkins script security/1.3
- version/jenkins script security/1.4
- version/jenkins script security/1.5
- version/jenkins script security/1.6
- version/jenkins script security/1.7
- version/jenkins script security/1.8
- version/jenkins script security/1.9
- version/jenkins script security/1.10
- version/jenkins script security/1.11
- version/jenkins script security/1.12
- version/jenkins script security/1.13
- version/jenkins script security/1.14
- version/jenkins script security/1.15
- version/jenkins script security/1.16
- version/jenkins script security/1.17
- version/jenkins script security/1.18
- package-manager/maven