CVE-2018-1000067: Server-Side Request Forgery in Jenkins

Summary

13/05/2022
Yes i
Moderate
5.3

CVE-2018-1000067: Server-Side Request Forgery in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.

< 2.89.4 >= 2.90, < 2.107

Fixed in 2.89.4 or 2.107, 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 is widely used for continuous integration and delivery. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core'.

Vulnerability Detail

The vulnerability, identified as CVE-2018-1000067, is an improper authorization issue in Jenkins versions 2.106 and earlier, as well as LTS 2.89.3 and earlier. It allows an attacker to exploit server-side request forgery (SSRF) and make Jenkins submit HTTP GET requests, obtaining limited information about the response. This vulnerability can potentially lead to unauthorized access and information 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.89.4 2.89.4
  • >= 2.90, < 2.107 2.107

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

In conclusion, the CVE-2018-1000067 vulnerability in Jenkins exposes the system to server-side request forgery (SSRF) attacks, potentially leading to unauthorized access and information disclosure. It is crucial to update Jenkins to the fixed versions mentioned to mitigate this vulnerability. For further support on vulnerability remediation, 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.

Server-side request forgery (SSRF) is a vulnerability that allows an attacker to make a server perform arbitrary HTTP requests on their behalf.

This vulnerability in Jenkins can lead to unauthorized access and information disclosure.

Jenkins versions 2.106 and earlier, as well as LTS 2.89.3 and earlier, are affected.

To fix this vulnerability, upgrade Jenkins to the recommended fixed versions mentioned earlier.

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.89.4 2.89.4
  • >= 2.90, < 2.107 2.107

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