Deploy WeblogicApplication · Jenkins
CVE-2019-10464
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 Deploy WebLogic Plugin allows attackers to connect to an attacker-specified URL using attacker-specified credentials, or determine whether a file or directory with an attacker-specified path exists 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 confidenceA cross-site request forgery (CSRF) vulnerability in the Jenkins Deploy WebLogic Plugin allows authenticated users (or those with session access) to be tricked into making unintended requests. Attackers can force Jenkins to connect to attacker-specified URLs using attacker-specified credentials, or probe the Jenkins master file system to determine if files/directories exist 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
Deploy WeblogicApplication
<= 4.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 Deploy WebLogic Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Deploy WebLogic', or run: jenkins-cli or check $JENKINS_HOME/plugins for the deploy-weblogic directoryAffected if The plugin is present in the plugins list
-
Determine the installed version of Deploy WebLogic PluginIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate the version column for Deploy WebLogic Plugin, or inspect $JENKINS_HOME/plugins/deploy-webossic/META-INF/MANIFEST.MFAffected if The version number is 4.1 or lower
-
Identify if any Jenkins jobs use the Deploy WebLogic PluginSearch job configurations for the 'deployer' build step or 'Deploy WebLogic' post-build action, or use Jenkins CLI: jenkins-cli.jar list-jobs | xargs -I {} jenkins-cli.jar get-job {} | grep -i weblogicAffected if Any job configuration references Deploy WebLogic plugin functionality
-
Check if CSRF protection is enabled in Jenkins global securityNavigate to Manage Jenkins > Configure Global Security and verify 'CSRF Protection' is enabled with a crumb issuer selected (Default Crumb Issuer or compatible)Affected if CSRF protection is disabled or no crumb issuer is configured, and the plugin is installed and version-vulnerable
You are affected if the Deploy WebLogic Plugin version is 4.1 or lower, the plugin is installed, and CSRF protection is disabled in Jenkins global security settings.
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 dataEnable CSRF protection (crumb library) in Jenkins global security settings and update the Deploy WebLogic Plugin to the latest patched version that addresses this vulnerability.
Fix this in Deploy Weblogic
Scoped from the published advisory
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10464 — 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-10464 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