WaratekVRT Sign in

CVE-2017-1000362 Jenkins

Affected softwareJenkins
Severity9.8 Critical CVSS 3.0 2 scores
Fixed in2.32.2, 2.44
WeaknessInformation exposure (CWE-200)
Published17 Jul 2017
Updated17 Jun 2026

Description

The re-key admin monitor was introduced in Jenkins 1.498 and re-encrypted all secrets in JENKINS_HOME with a new key. It also created a backup directory with all old secrets, and the key used to encrypt them. These backups were world-readable and not removed afterwards. Jenkins now deletes the backup directory, if present. Upgrading from before 1.498 will no longer create a backup directory. Administrators relying on file access permissions in their manually created backups are advised to check them for the directory $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups, and delete it if present.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 9 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS 1.7% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: jenkinsci/jenkins 0be33cf.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

CVSS

9.8 CRITICAL v3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.0 9.8 CRITICAL CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H NVD Primary published
CVSS 2.0 5.0 none AV:N/AC:L/Au:N/C:P/I:N/A:N NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.jenkins-ci.main:jenkins-core 1.498 2.32.2 unbounded
org.jenkins-ci.main:jenkins-core 2.40 2.44 unbounded

Products and versions

2 products, 3 version entries
SourceVendorProductSchemeAffected versions
nvd jenkins jenkins generic ≤ 1.498
osv org.jenkins-ci.main jenkins-core generic ≥ 1.498 and < 2.32.2 · ≥ 2.40 and < 2.44

References

URLTags
https://github.com/jenkinsci/jenkins/commit/0be33cf7328fad6a7596ce9505a74561a8b1eb85 WEB
https://github.com/jenkinsci/jenkins/commit/a572450f039fdb99410fcf6eb0ba307bd69ea458 WEB
https://github.com/jenkinsci/jenkins PACKAGE
https://jenkins.io/security/advisory/2017-02-01 WEB
https://jenkins.io/security/advisory/2017-02-01/ Vendor Advisory

Timeline

Published2017-07-17By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.