CVE-2016-0790
Published on: 04/07/2016 12:00:00 AM UTC
Last Modified on: 03/23/2021 11:27:13 PM UTC
Certain versions of Jenkins from Jenkins contain the following vulnerability:
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.
- CVE-2016-0790 has been assigned by
[email protected] to track the vulnerability - currently rated as MEDIUM severity.
CVSS3 Score: 5.3 - MEDIUM
Attack Vector ⓘ |
Attack Complexity |
Privileges Required |
User Interaction |
|
---|---|---|---|---|
NETWORK | LOW | NONE | NONE | |
Scope | Confidentiality Impact |
Integrity Impact |
Availability Impact |
|
UNCHANGED | LOW | NONE | NONE |
CVSS2 Score: 5 - MEDIUM
Access Vector ⓘ |
Access Complexity |
Authentication |
---|---|---|
NETWORK | LOW | NONE |
Confidentiality Impact |
Integrity Impact |
Availability Impact |
PARTIAL | NONE | NONE |
CVE References
Description | Tags ⓘ | Link |
---|---|---|
Red Hat Customer Portal | web.archive.org text/html Inactive LinkNot Archived |
![]() |
Red Hat Customer Portal | access.redhat.com text/html |
![]() |
Jenkins Security Advisory 2016-02-24 - Security Advisories - Jenkins Wiki | Patch Vendor Advisory wiki.jenkins-ci.org text/html |
![]() |
There are currently no QIDs associated with this CVE
Known Affected Configurations (CPE V2.3)
Type | Vendor | Product | Version | Update | Edition | Language |
---|---|---|---|---|---|---|
Application | Jenkins | Jenkins | All | All | All | All |
Application | Jenkins | Jenkins | All | All | All | All |
Application | Redhat | Openshift | 3.1 | All | All | All |
Application | Redhat | Openshift | 3.1 | All | All | All |
- cpe:2.3:a:jenkins:jenkins:*:*:*:*:lts:*:*:*:
- cpe:2.3:a:jenkins:jenkins:*:*:*:*:*:*:*:*:
- cpe:2.3:a:redhat:openshift:3.1:*:*:*:enterprise:*:*:*:
- cpe:2.3:a:redhat:openshift:3.1:*:*:*:enterprise:*:*:*:
No vendor comments have been submitted for this CVE