CVE-2016-0790
UnknownEPSS 2.10%
Last modified
CVE-2016-0790 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.10% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Jenkins | Jenkins | <= 1.642.1 |
| Redhat | Openshift | 3.1 |
| Jenkins | Jenkins | <= 1.649 |
References
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24Patch, Vendor Advisory
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-0790?
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.
How severe is CVE-2016-0790?
Severity scoring for CVE-2016-0790 is pending analysis. The EPSS model estimates a 2.10% probability of exploitation in the next 30 days.
How do I fix CVE-2016-0790?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2016-0790?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST