Xebialabs Xl DeployApplication · Jenkins
CVE-2021-21664
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 · uneditedAn incorrect permission check in Jenkins XebiaLabs XL Deploy Plugin 10.0.1 and earlier allows attackers with Generic Create permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing Username/password credentials stored in Jenkins.
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 · moderate confidenceThis is an incorrect permission check vulnerability in the XebiaLabs XL Deploy plugin for Jenkins (versions 10.0.1 and earlier). Attackers with Generic Create permission can bypass intended access controls to specify arbitrary URLs and credential IDs, enabling them to exfiltrate stored username/password credentials from Jenkins. This represents a privilege escalation and credential theft vector.
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
Xebialabs Xl DeployApplication
<= 10.0.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 if XL Deploy plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'XebiaLabs' or 'XL Deploy' in the list of installed pluginsAffected if Plugin is present in the installed plugins list
-
Determine installed plugin versionIn the Installed Plugins list, locate the XL Deploy or XebiaLabs plugin and note the Version columnAffected if Version is 10.0.1 or earlier (e.g., 10.0.1, 10.0, 9.x, etc.)
-
Check if plugin configuration existsNavigate to Manage Jenkins > Configure System and look for 'XL Deploy' or 'XebiaLabs' configuration section. Verify if any XL Deploy servers are configured with URLs and credential IDsAffected if Plugin is configured with XL Deploy server URLs and credential bindings
-
Identify users with Generic Create permissionNavigate to Manage Jenkins > Manage Users and cross-reference with Manage Jenkins > Manage and Assign Roles (or legacy authorization if used). Identify accounts granted 'Generic Create' permissionAffected if Any user account holds Generic Create permission, especially if not explicitly required for that user's role
You are affected if the XebiaLabs XL Deploy plugin version 10.0.1 or earlier is installed and any user possesses Generic Create permission, as the permission bypass can be exploited to access configured credentials.
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.
From vendor dataUpgrade XebiaLabs XL Deploy plugin to version 10.0.2 or later to obtain the corrected permission check. Additionally, audit user permissions to ensure Generic Create access is granted only to necessary personnel.
Fix this in Xebialabs Xl Deploy
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21664 — 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-21664 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