JenkinsApplication
CVE-2021-21694
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#toURI, FilePath#hasSymlink, FilePath#absolutize, FilePath#isDescendant, and FilePath#get*DiskSpace do not check any permissions in Jenkins 2.318 and earlier, LTS 2.303.2 and earlier.
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 confidenceThe Jenkins FilePath class has multiple methods (toURI, hasSymlink, absolutize, isDescendant, and get*DiskSpace) that perform file system operations without any permission checks. This allows unauthenticated or unauthorized users to potentially access sensitive file system information, enumerate symlinks, or obtain disk space information about arbitrary paths.
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 your Jenkins versionNavigate to Manage Jenkins > About Jenkins or access /api/json?tree=version to retrieve the installed version number.Affected if The version is below 2.303.3 (for LTS) or below 2.319 (for weekly releases)
-
Verify if anonymous or unauthenticated access is enabledNavigate to Manage Jenkins > Configure Global Security and review the Authorization section. Check if Anonymous users have any permissions or if the security realm allows unauthenticated access.Affected if Anonymous users have any permissions or unauthenticated access is permitted to the Jenkins UI or API
-
Check if CLI or API access is available without authenticationReview Manage Jenkins > Configure Global Security > CLI section. Verify whether the CLI is accessible or if remote API access permits unauthenticated calls.Affected if CLI or remote API is accessible to unauthenticated users
-
Identify exposed FilePath methods via APIUse a tool like curl to query the Jenkins API without credentials: curl -s http://JENKINS_URL/api/json?tree= -H "Authorization: Basic cmVhZGVyOnBhc3N3b3Jk" (or without auth header). Check if responses return successfully without authentication.Affected if API calls return successful responses without valid authentication
You are affected if your Jenkins version is below 2.303.3 (LTS) or 2.319 (weekly) AND anonymous or unauthenticated users can access the CLI, API, or UI.
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 later (or LTS 2.303.3 or later) which adds permission checks to these FilePath methods.
Jenkins 2.319 (weekly) or Jenkins 2.303.3 LTS
- Back up your Jenkins home directory (JENKINS_HOME) including all jobs, configurations, and plugins
- Review the Jenkins 2.319 and 2.303.3 LTS release notes at www.jenkins.io for any relevant changes or known issues
- Download the appropriate Jenkins WAR file (2.319 for weekly, or 2.303.3 LTS for the stable release line) from the official Jenkins distribution repository
- Stop the Jenkins service
- Replace the existing jenkins.war file in your Jenkins installation directory with the new version
- Start the Jenkins service
- Verify the upgrade was successful by checking the Jenkins version at /about/ and confirming all jobs and plugins function normally
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
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21694 — 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-21694 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