dbcve.org
JenkinsApplication

CVE-2017-1000362

CRITICAL · 9.8 CVSS v3.0 Published 2017-07-17
Fix available
A fix is available. Upgrade to after 1.498 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins versions 1.498 through the vulnerable version had a re-key admin monitor that created world-readable backup directories containing all old encrypted secrets and the keys used to encrypt them. These backups were stored in a predictable path ($JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups) and were not automatically removed, allowing unauthorized local users to access sensitive credential material.

MitigationImmediately check for and delete the backup directory at $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups if it exists, upgrade Jenkins to a patched version, and rotate all secrets/credentials that were stored in Jenkins as the encryption keys may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:<= 1.498

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jenkins version
    Locate the jenkins.war file or check the Jenkins web UI version number (typically shown on the bottom right of the main page) and compare it to the affected range 1.498 and below
    Affected if The installed Jenkins version is 1.498 or any earlier version
  2. Locate the backup directory
    Check if the directory $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups exists on the system where Jenkins is installed
    Affected if The directory exists on the filesystem
  3. Inspect backup directory contents
    List the contents of the backup directory (ls or dir command on the path)
    Affected if The directory contains any files - these would be the old encrypted secrets and encryption key backups
  4. Verify directory permissions
    Check the file permissions on the backup directory (using ls -la or equivalent)
    Affected if The directory is world-readable (permissions include 'others' having read access)

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.498
Interim mitigation

Immediately check for and delete the backup directory at $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups if it exists, upgrade Jenkins to a patched version, and rotate all secrets/credentials that were stored in Jenkins as the encryption keys may have been exposed.

Recommended fix High confidence

Jenkins > 1.498 (any later stable release)

  1. Check if the backup directory exists at $JENKINS_HOME/jenkins.security.RekeySecretAdminMonitor/backups
  2. If the directory exists, delete it entirely to remove exposed secrets and encryption keys
  3. Verify file permissions on the JENKINS_HOME directory to ensure only authorized users have access
  4. Consider upgrading Jenkins to a version greater than 1.498 to prevent future creation of such backup directories

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000362 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data