CVE-2018-1000192: Information Exposure in Jenkins
Summary
CVE-2018-1000192: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.107.3
>= 2.108, < 2.121
Fixed in 2.107.3 or 2.121, 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. It is widely used for continuous integration and delivery. The vulnerable package in question is org.jenkins-ci.main:jenkins-core, which is a core component of Jenkins responsible for its fundamental functionality.
Vulnerability Detail
The vulnerability, identified as CVE-2018-1000192, allows users with Overall/Read access to enumerate all installed plugins in Jenkins. This information exposure vulnerability exists in Jenkins versions 2.120 and older, as well as LTS versions 2.107.2 and older. The vulnerability is present in the AboutJenkins.java and ListPluginsCommand.java files. An unauthorized actor can exploit this vulnerability to gather sensitive information about the installed plugins, potentially aiding in further attacks or unauthorized access.
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.
-
< 2.107.32.107.3 -
>= 2.108, < 2.1212.121
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. It is advised to follow the recommended fix and upgrade to the fixed versions of Jenkins.
Conclusion
In conclusion, the CVE-2018-1000192 vulnerability in Jenkins allows users with Overall/Read access to enumerate all installed plugins, potentially exposing sensitive information. To mitigate this vulnerability, it is crucial to upgrade to the fixed versions of Jenkins. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
The vulnerability allows users with Overall/Read access to gather information about all installed plugins in Jenkins. This information can be potentially used by an unauthorized actor to plan further attacks or gain unauthorized access to the system.
Users of Jenkins versions 2.120 and older, as well as LTS versions 2.107.2 and older, are affected by this vulnerability.
There is no specific information about known exploits for this vulnerability. However, it is always recommended to promptly apply security patches and updates to mitigate any potential risks.
No specific mitigations are mentioned for this vulnerability. Upgrading to the fixed versions of Jenkins is the recommended approach to address this issue.
You can find more information about this vulnerability, including the CVE identifier, in the National Vulnerability Database (NVD) at https://nvd.nist.gov/vuln/detail/CVE-2018-1000192.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
