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.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2016-0790 from the MITRE CVE dictionary dictionary and NIST NVD.
| Base Score | 5.1 |
|---|---|
| Base Metrics | AV:N/AC:H/Au:N/C:P/I:P/A:P |
| Access Vector | Network |
| Access Complexity | High |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).
| Platform | Errata | Release Date |
|---|---|---|
| Red Hat OpenShift Enterprise 3.1 (jenkins) | RHSA-2016:0711 | 2016-05-03 |
| RHOSE Client 2.0 (jenkins) | RHSA-2016:1773 | 2016-08-24 |
Vulmon