First published: Mon Jan 29 2018(Updated: )
Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to a login command which allowed impersonating any Jenkins user. The `login` command available in the remoting-based CLI stored the encrypted user name of the successfully authenticated user in a cache file used to authenticate further commands. Users with sufficient permission to create secrets in Jenkins, and download their encrypted values (e.g. with Job/Configure permission), were able to impersonate any other Jenkins user on the same instance.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.main:jenkins-core | <=2.46.1 | 2.46.2 |
maven/org.jenkins-ci.main:jenkins-core | >=2.50<=2.56 | 2.57 |
Jenkins LTS | <=2.56 | |
Jenkins LTS | <=2.46.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000354 is classified as a medium severity vulnerability that allows impersonation of any Jenkins user.
To fix CVE-2017-1000354, upgrade to Jenkins version 2.46.2 or later, or to version 2.57 or later for non-LTS versions.
Jenkins versions 2.56 and earlier, as well as 2.46.1 LTS and earlier, are affected by CVE-2017-1000354.
The impact of CVE-2017-1000354 allows an attacker to impersonate any authenticated Jenkins user, potentially compromising sensitive information.
Yes, any Jenkins installation using version 2.56 or earlier, including 2.46.1 LTS and earlier, is vulnerable to CVE-2017-1000354.