CVE-2014-3665: Jenkins improperly ensures trust separation in org.jenkins-ci.main:jenkins-core

Summary

17/05/2022
Yes i
Moderate
Not published

CVE-2014-3665: Jenkins improperly ensures trust separation. Affects org.jenkins-ci.main:jenkins-core versions < 1.587. Fixed in 1.587. 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, org.jenkins-ci.main:jenkins-core, is a core component of Jenkins responsible for its basic functionality.

Vulnerability Detail

The vulnerability (CVE-2014-3665) in Jenkins versions prior to 1.587 and LTS before 1.580.1 arises from the improper trust separation between a master and its slaves. This flaw allows remote attackers with access to a slave to execute arbitrary code on the master. By exploiting this vulnerability, an attacker can gain unauthorized control over the Jenkins master, potentially leading to further compromise of the entire Jenkins environment.

How To Fix

Latest published version: 2.587 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.587

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. Upgrading to the fixed version is the only reliable solution.

Conclusion

The vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2014-3665) allows remote code execution on the Jenkins master, posing a significant security risk. It is crucial to upgrade Jenkins to version 1.587 or later to mitigate this vulnerability. Regular updates should be performed to ensure the ongoing security of the Jenkins installation. 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.

org.jenkins-ci.main:jenkins-core is a core component of Jenkins that provides its basic functionality.

This vulnerability allows remote attackers with access to a slave to execute arbitrary code on the Jenkins master, potentially compromising the entire Jenkins environment.

To fix this vulnerability, upgrade Jenkins to version 1.587 or later.

No, upgrading to the fixed version is the only reliable solution.

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 version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.587

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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