Skip to content
Fencer Intel
medium 6.5

CVE-2014-2062 json

Jenkins does not invalidate the API token when a user is deleted

published 12y ago modified 4mo ago also GHSA-vxc6-wvh8-fpxw , EUVD-2022-5453

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

Summary

Jenkins before 1.551 and LTS before 1.532.2 does not invalidate the API token when a user is deleted, which allows remote authenticated users to retain access via the token.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 1.532.2, 1.551
  • 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

Is CVE-2014-2062 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2062 updated cvss 4.0

jenkins: user tokens not invalidated correctly (SECURITY-89)

  • 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

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

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
>=1.533, <1.551
<1.532.2
1.551
1.532.2

Classification

Weakness
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.