CVE-2016-0790: Information Exposure

April 7, 2016 (updated January 5, 2018)

Jenkins does 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.

References

nvd.nist.gov/vuln/detail/CVE-2016-0790
wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24

Detect and mitigate CVE-2016-0790 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →