JenkinsApplication
CVE-2021-21692
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 · uneditedFilePath#renameTo and FilePath#moveAllChildrenTo in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier only check 'read' agent-to-controller access permission on the source path, instead of 'delete'.
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 confidenceJenkins FilePath#renameTo and FilePath#moveAllChildrenTo methods incorrectly check 'read' agent-to-controller access permission on the source path instead of 'delete' permission, allowing authenticated agents to move or rename files they should not have permission to modify.
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
< 2.303.3< 2.319CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Check Jenkins versionNavigate to Manage Jenkins > About Jenkins or check the jenkins.war file version. Run: java -jar jenkins.war --versionAffected if Version is lower than 2.303.3 LTS or lower than 2.319
-
Verify agent connectivityNavigate to Manage Jenkins > Manage Nodes. Check if any agents are configured and connected.Affected if Agents are configured and connected to the controller
-
Confirm FilePath operations in useReview any Pipeline scripts, Shared Libraries, or custom Groovy code that invoke FilePath.renameTo() or FilePath.moveAllChildrenTo() methodsAffected if Scripts or plugins actively use these FilePath methods on files the agent should not have delete access to
If Jenkins version is below 2.303.3 LTS or 2.319 AND authenticated agents are connected AND FilePath rename/move operations are being executed, the environment is affected by this permission bypass.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.303.32.319
Upgrade Jenkins to version 2.319 or LTS 2.303.3 or later which corrects the permission check to validate 'delete' access before file operations.
Jenkins 2.303.3 (LTS) or Jenkins 2.319 (weekly)
- 1. Back up your Jenkins home directory (JENKINS_HOME) and configuration before upgrading.
- 2. Schedule a maintenance window as Jenkins will restart during the upgrade.
- 3. Upgrade Jenkins to version 2.303.3 (LTS) or 2.319 (weekly release). For production environments, prefer LTS 2.303.3.
- 4. After upgrade, verify that Jenkins starts successfully and all critical plugins are functioning.
- 5. Test agent-to-controller file operations to confirm the permission check now correctly requires 'delete' permission instead of just 'read'.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21692 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-21692 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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