CVE-2018-1000863: Improper Limitation of a Pathname to a Restricted Directory in Jenkins

Summary

13/05/2022
Yes i
High
8.2

CVE-2018-1000863: Improper Limitation of a Pathname to a Restricted Directory 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

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 focus is 'org.jenkins-ci.main:jenkins-core'.

Vulnerability Detail

The vulnerability identified as CVE-2018-1000863 exists in Jenkins versions 2.153 and earlier, LTS 2.138.3 and earlier. It stems from a data modification flaw in the User.java and IdStrategy.java files. Attackers can exploit this vulnerability by submitting crafted user names, leading to an improper migration of user record storage formats. As a result, the victim may be prevented from logging into Jenkins. The severity of this vulnerability is rated as HIGH with a CVSS score of 8.2.

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

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the fixed versions of Jenkins.

Conclusion

In conclusion, the vulnerability CVE-2018-1000863 in Jenkins can be exploited to manipulate user record storage formats, potentially denying access to Jenkins. It is crucial to upgrade to the fixed versions of Jenkins 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 →

Share this vulnerability

FAQ

Jenkins is an open-source automation server used for continuous integration and delivery of software projects.

This vulnerability allows attackers to manipulate user record storage formats, potentially preventing users from logging into Jenkins.

You can use the Vulert Playground at Vulert Scanner to check if your Jenkins installation is affected by this vulnerability.

The CVSS score of this vulnerability is 8.2, indicating a high severity.

No, there is no known workaround. It is recommended to upgrade to the fixed versions of Jenkins.

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