Skip to content
Fencer Intel
medium 6.8

CVE-2014-3665 json

Jenkins improperly ensures trust separation

published 2015-11-25 10 y ago modified 2026-06-17 4 mo ago also GHSA-66cr-6whx-732p , EUVD-2022-2725

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

Jenkins before 1.587 and LTS before 1.580.1 do not properly ensure trust separation between a master and slaves, which might allow remote attackers to execute arbitrary code on the master by leveraging access to the slave.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 1.587
  • jenkins-plugin-openshift openshift 2.0 0.6.40.1-0.el6op
  • jenkins openshift 2.0 1.565.3-1.el6op
  • openshift-origin-cartridge-jenkins openshift 2.0 1.20.3.5-1.el6op

red hat advisories RHBA-2014:1630

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-3665 updated cvss 6.8

jenkins: remote code execution from slaves (SECURITY-144)

  • Red Hat OpenShift Enterprise 1 jenkins
    affected: no fix planned “Will not fix”
  • Red Hat RHOSE Node 2.1 jenkins 1.565.3-1.el6op, jenkins-plugin-openshift 0.6.40.1-0.el6op, openshift-origin-cartridge-jenkins 1.20.3.5-1.el6op
    fixed: vendor fix RHBA-2014:1630

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.50% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<1.587
1.587

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.