Vulnerabilities · 2019 · Jenkins
CVE-2019-10320
Jenkins Credentials vulnerability
Jenkins Credentials Plugin 2.1.18 and earlier allowed users with permission to create or update credentials to confirm the existence of files on the Jenkins master with an attacker-specified path, and obtain the certificate content of files containing a PKCS#12 certificate.
Affected products
Credentials. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Jenkins Credentials runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- jenkins.io/security/advisory/2019-05-21/#SECURITY-1322 · Mitigation
- seclists.org/fulldisclosure/2019/May/39
- www.openwall.com/lists/oss-security/2019/05/21/1
- www.securityfocus.com/bid/108462
- access.redhat.com/errata/RHBA-2019:1605
- access.redhat.com/errata/RHSA-2019:1636
- wwws.nightwatchcybersecurity.com/2019/05/23/exploring-the-file-system-via-jenkins-credenti
- nvd.nist.gov/vuln/detail/CVE-2019-10320
- cve.org/CVERecord?id=CVE-2019-10320
More vulnerabilities in Jenkins products
CVE-2025-67643CVE-2025-67642CVE-2025-67641CVE-2025-67640CVE-2025-67639CVE-2025-67638CVE-2025-67637CVE-2025-67636All 1,739
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.