Groovy Plugin up to 2.59 Sandbox SandboxTransformer.java privileges management

Summaryinfo

A vulnerability, which was classified as critical, has been found in Groovy Plugin up to 2.59. This vulnerability affects unknown code in the library groovy-cps/lib/src/main/java/com/cloudbees/groovy/cps/SandboxCpsTransformer.java of the file groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java of the component Sandbox. Performing a manipulation results in privileges management. This vulnerability is cataloged as CVE-2018-1000866. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Groovy Plugin up to 2.59. It has been classified as critical. This affects an unknown functionality in the library groovy-cps/lib/src/main/java/com/cloudbees/groovy/cps/SandboxCpsTransformer.java of the file groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java of the component Sandbox. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.59 and earlier in groovy-sandbox/src/main/java/org/kohsuke/groovy/sandbox/SandboxTransformer.java, groovy-cps/lib/src/main/java/com/cloudbees/groovy/cps/SandboxCpsTransformer.java that allows attackers with Job/Configure permission, or unauthorized attackers with SCM commit privileges and corresponding pipelines based on Jenkinsfiles set up in Jenkins, to execute arbitrary code on the Jenkins master JVM

The bug was discovered 10/29/2018. The weakness was shared 12/10/2018 (Website). It is possible to read the advisory at jenkins.io. This vulnerability is uniquely identified as CVE-2018-1000866 since 12/10/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 42 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entry VDB-127778 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Groovy Plugin

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.31
• 2.32
• 2.33
• 2.34
• 2.35
• 2.36
• 2.37
• 2.38
• 2.39
• 2.40
• 2.41
• 2.42
• 2.43
• 2.44
• 2.45
• 2.46
• 2.47
• 2.48
• 2.49
• 2.50
• 2.51
• 2.52
• 2.53
• 2.54
• 2.55
• 2.56
• 2.57
• 2.58
• 2.59

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion