dbcve.org
Xebialabs Xl DeployApplication · Jenkins

CVE-2021-21665

HIGH · 8.8 CVSS v3.1 Published 2021-06-10
Fix available
A fix is available. Upgrade to after 10.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) vulnerability in Jenkins XebiaLabs XL Deploy Plugin 10.0.1 and earlier allows attackers 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 · high confidence

This is a CSRF vulnerability in the Jenkins XebiaLabs XL Deploy Plugin versions 10.0.1 and earlier. An authenticated attacker can craft malicious requests that cause Jenkins to connect to an attacker-controlled URL using attacker-specified credential IDs, ultimately allowing capture of stored username/password credentials. The attack exploits the lack of CSRF tokens or proper request validation in the plugin's credential-handling functionality.

MitigationUpdate the XebiaLabs XL Deploy Plugin to a version newer than 10.0.1. Review and rotate any credentials that may have been exposed, and monitor for unauthorized access.

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
Affected:<= 10.0.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify XL Deploy plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for xldeploy folder
    Affected if The XebiaLabs XL Deploy plugin appears in the installed plugins list
  2. Check installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the XebiaLabs XL Deploy plugin and note the version number
    Affected if The installed version is 10.0.1 or earlier
  3. Identify stored XL Deploy credentials
    Navigate to Jenkins > Credentials > System > Global credentials, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-credentials to list stored credentials
    Affected if Any XL Deploy credentials (username/password pairs) are stored in Jenkins credentials store
  4. Check plugin configuration in job definitions
    Review configured Jenkins jobs that use XL Deploy plugin, or check $JENKINS_HOME/jobs/*/config.xml for xldeploy-related configuration blocks
    Affected if Any job or configuration references the XL Deploy plugin and uses stored credential IDs

If the XebiaLabs XL Deploy plugin version 10.0.1 or earlier is installed AND XL Deploy credentials are configured in Jenkins, the environment is affected by this CSRF vulnerability.

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 10.0.1
Interim mitigation

Update the XebiaLabs XL Deploy Plugin to a version newer than 10.0.1. Review and rotate any credentials that may have been exposed, and monitor for unauthorized access.

Recommended fix Moderate confidence

XebiaLabs XL Deploy Plugin version 10.0.2 or later

  1. 1. Navigate to Jenkins plugin management interface
  2. 2. Find 'XebiaLabs XL Deploy' plugin in the available plugins list
  3. 3. Upgrade the plugin to version 10.0.2 or later
  4. 4. Restart Jenkins if required
  5. 5. Verify the plugin upgraded successfully and functionality works as expected

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

Fix this in Xebialabs Xl Deploy Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21665 — 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-2021-21665 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