CVE-2017-1000362: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
Summary
CVE-2017-1000362: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
>= 1.498, < 2.32.2
>= 2.40, < 2.44
Fixed in 2.32.2 or 2.44, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Jenkins is an open-source automation server that enables developers to build, test, and deploy their software projects. The 'jenkins-core' package is a fundamental component of Jenkins, providing core functionalities and features. This vulnerability affects versions 1.498 to 2.32.1 and versions 2.40 to 2.43 of the 'jenkins-core' package.
Vulnerability Detail
The vulnerability, identified as CVE-2017-1000362, involves the exposure of sensitive information to unauthorized actors in Jenkins. In versions prior to 1.498, the re-key admin monitor introduced a new encryption key and created a backup directory containing all old secrets and the encryption key used. Unfortunately, these backups were world-readable and not removed afterward, potentially allowing unauthorized access to sensitive information. Jenkins now deletes the backup directory if present. Administrators relying on file access permissions in their manually created backups should check for the directory '$JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups' and delete it if found.
How To Fix
Latest published version: 2.587 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 1.498, < 2.32.22.32.2 -
>= 2.40, < 2.442.44
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The exposure of sensitive information to unauthorized actors in Jenkins can have severe consequences for the security and integrity of Jenkins instances. It is crucial to upgrade the 'jenkins-core' package to the fixed versions mentioned to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
The vulnerability allows unauthorized actors to access sensitive information stored in the backup directory, potentially leading to unauthorized disclosure of secrets and compromising the security of Jenkins instances.
Versions 1.498 to 2.32.1 and versions 2.40 to 2.43 of the 'jenkins-core' package are affected by this vulnerability.
Yes, upgrading the 'jenkins-core' package to version 2.32.2 or above (for versions 1.498 to 2.32.1) or version 2.44 or above (for versions 2.40 to 2.43) fixes this vulnerability.
No specific workarounds are mentioned for this vulnerability.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the 'pom.xml' file for analysis.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
