Openshift DeployerApplication · Jenkins
CVE-2019-1003080
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 OpenShift Deployer Plugin in the DeployApplication.DeployApplicationDescriptor#doCheckLogin 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 confidenceCross-site request forgery (CSRF) vulnerability in Jenkins OpenShift Deployer Plugin's DeployApplication.DeployApplicationDescriptor#doCheckLogin form validation method allows authenticated attackers to trigger connections from the Jenkins server to attacker-controlled servers by tricking a user with form validation access into visiting a malicious page.
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
Openshift DeployerApplication
<= 1.2.0CVSS 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 OpenShift Deployer Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'OpenShift Deployer' or check the $JENKINS_HOME/plugins/ directory for the openshift-deployer plugin folderAffected if The plugin appears in the installed plugins list or the plugin folder exists
-
Identify the installed plugin versionClick on the OpenShift Deployer Plugin in the Installed tab to view its version, or inspect the manifest file (META-INF/MANIFEST.MF) inside the plugin hpi file in the plugins directoryAffected if The version is 1.2.0 or lower
-
Confirm the plugin is enabled and activeGo to Manage Jenkins > Configure Global Security > Agents and check if the OpenShift Deployer plugin is loaded, or verify the plugin .jpi file exists and is not disabled (no .jpi.disabled file)Affected if The plugin is enabled and loaded in Jenkins runtime
-
Check if form validation access is available to attackersThe doCheckLogin method in DeployApplicationDescriptor is called during form validation. Verify if any users with Overall/Read or Extended Read access exist in Jenkins who could be tricked into visiting a malicious pageAffected if Any authenticated user with form validation access exists in the Jenkins instance
You are affected if the OpenShift Deployer Plugin version is 1.2.0 or lower, the plugin is enabled, and any user with form validation access exists who could be tricked into triggering the vulnerable doCheckLogin method.
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 the OpenShift Deployer Plugin to the latest version containing the CSRF fix. If no patch is available, disable the plugin or implement Jenkins' built-in CSRF protection via crumb tokens.
Fix this in Openshift Deployer
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-1003080 — 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-1003080 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