CVE-2016-0790 Exposure of Sensitive Information in Jenkins Core
Remote attackers can brute-force API tokens due to non-constant-time verification, potentially leading to unauthorized access.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2016-0790?
CVE-2016-0790 is a medium-severity vulnerability in Jenkins Jenkins, published on 7 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2016-0790?
2 open source packages ship an affected version, including org.jenkins-ci.main:jenkins-core. It affects 2 products.
| Package | Affected | Fixed in |
|---|---|---|
org.jenkins-ci.main:jenkins-core Maven | All versions | 1.650 |
org.jenkins-ci.main:jenkins-core Maven | All versions | 1.650 |
Products include Jenkins Jenkins, Redhat Openshift.
How do I fix CVE-2016-0790?
Upgrade org.jenkins-ci.main:jenkins-core to 1.650 or later.
Is CVE-2016-0790 being exploited?
There is no known exploitation of CVE-2016-0790 in the wild and no public exploit code.
Other vulnerabilities in Jenkins Jenkins
- CVE-2024-23897 Jenkins Command Line Interface (CLI) Path Traversal
- CVE-2018-1000861 Jenkins Stapler Web Framework Deserialization of Untrusted Data
- CVE-2017-1000353 Jenkins Remote Code Execution
- CVE-2015-5317 Jenkins User Interface (UI) Information Disclosure
- CVE-2021-21690 Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins
Sources
Also known as GHSA-jgpr-qrw2-6gp3.