First published: Thu Feb 25 2016(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/Jenkins | <1.650 | 1.650 |
redhat/Jenkins | <1.642.2 | 1.642.2 |
Jenkins Jenkins | <=1.642.1 | |
redhat openshift | =3.1 | |
Jenkins Jenkins | <=1.649 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-0790 is classified as a moderate severity vulnerability due to its potential for remote exploitation.
To fix CVE-2016-0790, update Jenkins to version 1.650 or later, or update to Jenkins LTS version 1.642.2 or later.
The impact of CVE-2016-0790 allows attackers to potentially determine user-specific API tokens through brute-force methods.
Jenkins versions prior to 1.650 and LTS versions before 1.642.2 are affected by CVE-2016-0790.
Yes, CVE-2016-0790 specifically affects Jenkins and Red Hat OpenShift versions mentioned in the vulnerability report.