[JIRA] (JENKINS-55557) Support oAuth2.0 state parameter

3 views
Skip to first unread message

ikakavas+jenkinsio@protonmail.com (JIRA)

unread,
Jan 13, 2019, 12:00:02 PM1/13/19
to jenkinsc...@googlegroups.com
Ioannis Kakavas created an issue
 
Jenkins / Improvement JENKINS-55557
Support oAuth2.0 state parameter
Issue Type: Improvement Improvement
Assignee: Sam Gleske
Components: github-oauth-plugin
Created: 2019-01-13 16:59
Priority: Major Major
Reporter: Ioannis Kakavas

The current implementation does not support the `state` parameter in the oAuth2 authorization request it sends to the Github AS when attempting to authorize the plugin for a user.  As such, it is vulnerable to CSRF attacks against redirect URI as described in [1]

 The state parameter is supported by the Github API [2] , so support could be added in the github-oauth-plugin also.

 

[1] https://tools.ietf.org/html/rfc6819#section-4.4.1.8
[2] https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ikakavas+jenkinsio@protonmail.com (JIRA)

unread,
Jan 14, 2019, 4:56:02 AM1/14/19
to jenkinsc...@googlegroups.com

sam.mxracer@gmail.com (JIRA)

unread,
Aug 6, 2019, 12:08:01 AM8/6/19
to jenkinsc...@googlegroups.com
Sam Gleske resolved as Fixed
 

Resolving as fixed in 0.33 (originally attempted rolling out 0.32 but it had critical authorization bugs).

In the future, please do not disclose security vulnerabilities like this in the public issue tracker. Responsibly disclose by following https://jenkins.io/security/

Change By: Sam Gleske
Status: Open Resolved
Resolution: Fixed

sam.mxracer@gmail.com (JIRA)

unread,
Aug 6, 2019, 12:12:02 AM8/6/19
to jenkinsc...@googlegroups.com

Regardless, thanks for the fix.

sam.mxracer@gmail.com (JIRA)

unread,
Aug 6, 2019, 12:12:02 AM8/6/19
to jenkinsc...@googlegroups.com
Sam Gleske edited a comment on Improvement JENKINS-55557
Regardless, thanks Thanks for the fix.
Reply all
Reply to author
Forward
0 new messages