CVE-2018-1999045: Improper Authentication in Jenkins

Summary

14/05/2022
Yes i
Moderate
5.4

CVE-2018-1999045: Improper Authentication in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.

< 2.121.3 >= 2.122, < 2.138

Fixed in 2.121.3 or 2.138, 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 Your last release was probably never penetration tested 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, org.jenkins-ci.main:jenkins-core, is a core component of Jenkins responsible for its basic functionality.

Vulnerability Detail

The vulnerability, identified as CVE-2018-1999045, is an improper authentication issue in Jenkins. Specifically, it exists in versions 2.137 and earlier, 2.121.2 and earlier in SecurityRealm.java and TokenBasedRememberMeServices2.java. Attackers with a valid cookie can remain logged in even if the 'remember me' feature is disabled. This can lead to unauthorized access and potential misuse of Jenkins resources.

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.121.3 2.121.3
  • >= 2.122, < 2.138 2.138

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. However, users can mitigate the risk by ensuring that the 'remember me' feature is enabled and monitoring their Jenkins instance for any unauthorized activity.

Conclusion

In conclusion, the vulnerability CVE-2018-1999045 in Jenkins allows attackers to bypass authentication and gain unauthorized access to Jenkins resources. It is crucial to upgrade to the fixed versions of Jenkins to ensure the security and integrity of the system. 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.

The vulnerable package is org.jenkins-ci.main:jenkins-core, which is a core component of Jenkins responsible for its basic functionality.

This vulnerability allows attackers with a valid cookie to remain logged in even if the 'remember me' feature is disabled, potentially leading to unauthorized access and misuse of Jenkins resources.

To fix this vulnerability, it is recommended to upgrade to the fixed versions of Jenkins (2.121.3 or newer for versions 2.121.2 and earlier, and 2.138 or newer for versions 2.122 and later).

While no specific workaround is mentioned, users can mitigate the risk by enabling the 'remember me' feature and monitoring their Jenkins instance for any unauthorized activity.

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.121.3 2.121.3
  • >= 2.122, < 2.138 2.138

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