CVE-2018-1000862: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins

Summary

14/05/2022
Yes i
Moderate
4.3

CVE-2018-1000862: Exposure of Sensitive Information to an Unauthorized Actor in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.

< 2.138.4 >= 2.140, < 2.154

Fixed in 2.138.4 or 2.154, depending on the release line you run. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Jenkins is an open-source automation server that enables developers to build, test, and deploy their software projects. It provides a wide range of features and plugins to support continuous integration and delivery. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core'. This package is a fundamental component of Jenkins and is responsible for core functionality such as job scheduling, build execution, and workspace management.

Vulnerability Detail

The vulnerability identified as CVE-2018-1000862 affects Jenkins versions 2.153 and earlier, as well as LTS 2.138.3 and earlier. It resides in the 'DirectoryBrowserSupport.java' file and allows attackers with control over build output to browse the file system on agents running builds even after the build has completed. This exposure occurs through the workspace browser functionality. An unauthorized actor could exploit this vulnerability to gain access to sensitive information stored on the agent's file system, potentially leading to further compromise or unauthorized data disclosure.

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.138.4 2.138.4
  • >= 2.140, < 2.154 2.154

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, users can disable the workspace browser functionality in Jenkins. This can be achieved by navigating to the Jenkins master's configuration page, locating the 'Enable workspace browser' option, and disabling it. However, this workaround may limit certain features and hinder the ability to browse workspace contents during and after builds.

Conclusion

The exposure of sensitive information to unauthorized actors in Jenkins versions 2.153 and earlier, as well as LTS 2.138.3 and earlier, poses a significant risk to the security and integrity of CI/CD pipelines. It is crucial for users to upgrade to the recommended versions or apply the provided workaround to mitigate this vulnerability. Regularly updating Jenkins and its dependencies is essential to ensure a secure development and deployment environment. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →

Share this vulnerability

FAQ

The vulnerability allows unauthorized actors to browse the file system on agents running builds, potentially exposing sensitive information. This could lead to unauthorized access, data leakage, or further compromise of the CI/CD pipeline.

Users of Jenkins versions 2.153 and earlier, as well as LTS 2.138.3 and earlier, are affected by this vulnerability if the 'DirectoryBrowserSupport.java' file is present in their installation.

At the time of this advisory, there are no known public exploits specifically targeting this vulnerability. However, it is essential to apply the recommended patches promptly to mitigate the risk.

Yes, the CVSS score for this vulnerability is 4.3, indicating a moderate severity level. It is crucial to address this vulnerability to prevent potential unauthorized access and information exposure.

Yes, you can utilize Vulert's playground at Vulert Scanner to check if your Jenkins installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, providing valuable insights without requiring access to the code or installation.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.

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.138.4 2.138.4
  • >= 2.140, < 2.154 2.154

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback