Xebialabs Xl DeployApplication · Jenkins
CVE-2019-10304
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 · uneditedA cross-site request forgery vulnerability in Jenkins XebiaLabs XL Deploy Plugin in the Credential#doValidateUserNamePassword form validation method allows attackers to initiate a connection to an attacker-specified server.
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 confidenceA cross-site request forgery (CSRF) vulnerability in the Jenkins XebiaLabs XL Deploy plugin's Credential#doValidateUserNamePassword form validation method allows authenticated users to be tricked into initiating connections to attacker-specified servers. The form validation endpoint lacks proper CSRF token (crumb) validation.
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
<= 7.5.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Verify XL Deploy plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'XL Deploy' or 'Xebialabs', or inspect the plugin directory $JENKINS_HOME/plugins/ for the xl-deploy plugin folderAffected if The XL Deploy plugin is present in the Jenkins installation
-
Determine installed XL Deploy plugin versionIn Jenkins UI: Manage Jenkins > Manage Plugins > Installed > XL Deploy plugin - note the version column. Alternatively, inspect $JENKINS_HOME/plugins/xl-deploy/META-INF/MANIFEST.MF for the Bundle-Version attributeAffected if The installed version is 7.5.3 or lower (any version <= 7.5.3)
-
Confirm plugin is enabled and loadedCheck Manage Jenkins > Manage Plugins > Installed tab - ensure XL Deploy shows as 'Enabled' and there are no errors in Manage Jenkins > System Information related to the pluginAffected if The plugin is enabled and loaded without errors
-
Verify the Credential form validation endpoint existsInspect the plugin's archived .hpi file for the Credential.java class containing the doValidateUserNamePassword method, or access the URL pattern /descriptorByName/XLDeployCredential/validateUserNamePassword if the plugin is activeAffected if The Credential#doValidateUserNamePassword form validation endpoint is accessible (which is the case when the plugin is installed and enabled)
You are affected if the XL Deploy plugin is installed, enabled, and its version is 7.5.3 or lower, as this version range lacks CSRF crumb validation on the Credential form validation endpoint.
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 dataUpdate to the latest version of the XL Deploy plugin which implements CSRF protection (crumb validation) on the Credential#doValidateUserNamePassword form validation method. Until patched, limit plugin access to trusted users only.
Fix this in Xebialabs Xl Deploy
Scoped from the published advisory
- Consultation1.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10304 — 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-2019-10304 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