Xebialabs Xl DeployApplication · Jenkins
CVE-2019-10305
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 missing permission check in Jenkins XebiaLabs XL Deploy Plugin in the Credential#doValidateUserNamePassword form validation method allows attackers with Overall/Read permission 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 confidenceThe XebiaLabs XL Deploy Plugin for Jenkins has a missing permission check in the Credential#doValidateUserNamePassword form validation method. While Jenkins permissions are enforced at the overall framework level, this specific method only requires Overall/Read permission (the lowest privilege level) rather than proper authentication or admin-level permissions. This allows any authenticated user with read access to trigger the Jenkins server to initiate network connections to attacker-controlled servers, enabling server-side request forgery (SSRF) style attacks.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Check if XebiaLabs XL Deploy plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'XebiaLabs XL Deploy' or 'xl-deploy'Affected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn the Installed plugins tab, locate the XebiaLabs XL Deploy plugin and note the version number displayed in the 'Version' columnAffected if The version number is 7.5.3 or lower
-
Verify Overall/Read permission is granted to usersNavigate to Jenkins > Manage Jenkins > Configure Global Security > Authorization section, or check individual/user permissions to see which users have Overall/Read accessAffected if Users other than administrators have Overall/Read permission enabled
-
Confirm the vulnerable credential validation method is accessibleAttempt to access the credential validation endpoint or verify the plugin's Credential#doValidateUserNamePassword method is exposed via the Jenkins UI under the XL Deploy plugin configurationAffected if The credential validation form is accessible without elevated permissions
A user is affected if the XebiaLabs XL Deploy plugin version 7.5.3 or lower is installed AND users with only Overall/Read permission can access the credential validation functionality.
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 to the patched version of the XebiaLabs XL Deploy Plugin that implements proper permission checks in the Credential#doValidateUserNamePassword method. Until patched, restrict Overall/Read permission to only trusted users and monitor for unusual outbound connections from the Jenkins server.
Fix this in Xebialabs Xl Deploy
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10305 — 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-10305 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