Bug 1542730 – CVE-2018-1000058 jenkins-plugin-workflow-support: Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1542730 - (CVE-2018-1000058) CVE-2018-1000058 jenkins-plugin-workflow-support: Arbitrary code execution due to incomplete sandbox protection in Pipeline: Supporting APIs Plugin

Summary:	CVE-2018-1000058 jenkins-plugin-workflow-support: Arbitrary code execution du...

Status:	CLOSED WONTFIX

Aliases:	CVE-2018-1000058

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20180205,repor...
Keywords:	Security

Depends On:
Blocks:	1542732
	Show dependency tree / graph

Reported:	2018-02-06 17:15 EST by Laura Pardo
Modified:	2018-02-15 22:03 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	jenkins-plugin-workflow-support 2.18
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-02-15 22:03:08 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Laura Pardo 2018-02-06 17:15:59 EST

A flaw was found in Jenkins Pipeline: Supporting APIs Plugin. Pipelines are subject to script security: Either the entire Pipeline needs to be approved, or it runs in a sandbox, with only whitelisted methods etc. allowed to be called. Methods related to Java deserialization like readResolve implemented in Pipeline scripts were not subject to sandbox protection, and could therefore execute arbitrary code. This could be exploited e.g. by regular Jenkins users with the permission to configure Pipelines in Jenkins, or by trusted committers to repositories containing Jenkinsfiles.


References:
https://jenkins.io/security/advisory/2018-02-05/ [SECURITY-699 / CVE-2018-1000058]

Note You need to log in before you can comment on or make changes to this bug.