Websphere DeployerApplication · Jenkins
CVE-2019-16560
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 WebSphere Deployer Plugin 1.6.1 and earlier allows attackers to perform connection tests and determine whether files with an attacker-specified path exist on the Jenkins master file system.
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 confidenceJenkins WebSphere Deployer Plugin versions 1.6.1 and earlier lack proper CSRF protection (crumb) on form submissions. This allows attackers to trick authenticated Jenkins users into performing unintended actions, specifically testing WebSphere connections and probing the Jenkins master filesystem to confirm existence of files at attacker-specified 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
Websphere DeployerApplication
<= 1.6.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WebSphere Deployer plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins/ directory for a file starting with 'websphere-deployer' (with .jpi or .hpi extension).Affected if The plugin file exists in the plugins directory or is listed in the Installed plugins list.
-
Determine installed plugin versionOpen the WebSphere Deployer plugin file (.jpi or .hpi) as a ZIP archive and read the MANIFEST.MF file to find the Implementation-Version, or view the version column in Manage Jenkins > Manage Plugins > Installed.Affected if The reported version is 1.6.1 or earlier.
-
Check for active plugin usageReview Jenkins jobs and freestyle configurations for uses of the 'WebSphere Deployer' plugin (look for build steps or publishers referencing WebSphere). Also check Manage Jenkins > Configure System for any WebSphere-related configuration.Affected if Any job, build step, or system configuration references the WebSphere Deployer plugin functionality.
-
Verify authenticated user access existsReview Manage Jenkins > Manage Users to confirm there is more than one user account, or that external authentication (LDAP, etc.) is enabled with active users.Affected if The Jenkins instance has authenticated users who can log in and create or modify jobs.
-
Confirm CSRF protection mechanism statusNavigate to Manage Jenkins > Configure Global Security and verify whether 'Crumb' CSRF protection is enabled (under CSRF Protection section).Affected if CSRF protection is enabled globally, but the vulnerability exists because the plugin lacks crumb support even when global CSRF protection is on.
A user is affected if WebSphere Deployer plugin version 1.6.1 or earlier is installed AND there are authenticated Jenkins users who could be tricked into submitting forms via the plugin.
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 WebSphere Deployer Plugin to version 1.6.2 or later, which includes proper CSRF token validation. If immediate upgrade is not possible, disable the plugin if unused and restrict Jenkins user access to trusted personnel only.
Fix this in Websphere Deployer
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16560 — 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-16560 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