Bug 1585989 – CVE-2018-1000184 jenkins-plugin-github: Server-side request forgery vulnerability (SECURITY-799)

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 1585989 - (CVE-2018-1000184) CVE-2018-1000184 jenkins-plugin-github: Server-side request forgery vulnerability (SECURITY-799)

Summary:	CVE-2018-1000184 jenkins-plugin-github: Server-side request forgery vulnerabi...

Status:	NEW

Aliases:	CVE-2018-1000184

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=20180604,repor...
Keywords:	Security

Depends On:	1588942
Blocks:	1585998
	Show dependency tree / graph

Reported:	2018-06-05 05:03 EDT by Adam Mariš
Modified:	2018-06-29 18:38 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	jenkins-plugin-github 1.29.0
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
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 Adam Mariš 2018-06-05 05:03:09 EDT

A form validation method in GitHub Plugin did not check the permission of the user accessing it, allowing anyone with Overall/Read access to Jenkins to cause Jenkins to send a POST request to a specified URL. If that request’s HTTP response code indicates success, the form validation is returning a generic success message, otherwise the HTTP status code is returned. Additionally, this form validation method did not require POST requests, resulting in a CSRF vulnerability.

External References:

https://jenkins.io/security/advisory/2018-06-04/

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