CVE-2016-0790: Infoleak
Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify API tokens, which makes it easier for remote attackers to determine API tokens via a brute-force approach.
Other sources
The following flaw was found in Jenkins:
The verification of user-provided API tokens with the expected value did not use a constant-time comparison algorithm, potentially allowing attackers to use statistical methods to determine valid API tokens using brute-force methods.
External References:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2016-0790?
CVE-2016-0790 is classified as a moderate severity vulnerability due to its potential for remote exploitation.
How do I fix CVE-2016-0790?
To fix CVE-2016-0790, update Jenkins to version 1.650 or later, or update to Jenkins LTS version 1.642.2 or later.
What is the impact of CVE-2016-0790?
The impact of CVE-2016-0790 allows attackers to potentially determine user-specific API tokens through brute-force methods.
Which versions of Jenkins are affected by CVE-2016-0790?
Jenkins versions prior to 1.650 and LTS versions before 1.642.2 are affected by CVE-2016-0790.
Is CVE-2016-0790 related to any specific software products?
Yes, CVE-2016-0790 specifically affects Jenkins and Red Hat OpenShift versions mentioned in the vulnerability report.