Jenkins session fixation vulnerability
Research is free — Hunters explains how the bug works, the root-cause code pattern, how the fix addresses it, and how to test whether a target is affected, in chat. Investigate & write exploit is a paid run — the engine reads the advisory and fix commits, then builds and validates a working proof-of-concept exploit with reproduction steps.
Affected versions
1.533 → fixed in 1.5510 → fixed in 1.532.2
Details
Session fixation vulnerability in Jenkins before 1.551 and LTS before 1.532.2 allows remote attackers to hijack web sessions via vectors involving the "override" of Jenkins cookies.
The fix
[FIXED SECURITY-75] Invalidate session after login to avoid
core/src/main/java/hudson/security/AuthenticationProcessingFilter2.java+1 −0
@@ -85,6 +85,7 @@ protected void onSuccessfulAuthentication(HttpServletRequest request, HttpServle// HttpSessionContextIntegrationFilter stores the updated SecurityContext object into this session later// (either when a redirect is issued, via its HttpResponseWrapper, or when the execution returns to its// doFilter method.+request.getSession().invalidate();request.getSession();}
References
- ADVISORYhttps://nvd.nist.gov/vuln/detail/CVE-2014-2066
- WEBhttps://github.com/jenkinsci/jenkins/commit/8ac74c350779921598f9d5edfed39dd35de8842a
- PACKAGEhttps://github.com/jenkinsci/jenkins
- WEBhttps://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-02-14
- WEBhttp://www.openwall.com/lists/oss-security/2014/02/21/2