Openshift DeployerApplication · Jenkins
CVE-2019-1003081
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 OpenShift Deployer Plugin in the DeployApplication.DeployApplicationDescriptor#doCheckLogin 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 confidenceMissing permission check in Jenkins OpenShift Deployer Plugin's DeployApplication.DeployApplicationDescriptor#doCheckLogin form validation method allows authenticated users with Overall/Read permission (the lowest privilege) to trigger server connections to attacker-specified URLs, resulting in a Server-Side Request Forgery (SSRF) vulnerability.
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
- 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.
-
Verify OpenShift Deployer plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and look for 'OpenShift Deployer' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Installed plugins list, locate the OpenShift Deployer plugin and note the version number displayed in the Version columnAffected if The version number is 1.2.0 or lower
-
Confirm plugin is actively configuredNavigate to Manage Jenkins > Configure System and look for OpenShift Deployer configuration section, or check job configurations for OpenShift Deployer build stepsAffected if The plugin has an active configuration or is used in any job definitions
-
Verify accessible form validation endpointThe vulnerability exists in the doCheckLogin form validation method. In a default Jenkins setup, this endpoint would be accessible at /descriptorByName/openshiftdeployer.OpenShiftDeployerPublisher/doCheckLogin to any authenticated user with Overall/Read permissionAffected if The plugin is installed and Jenkins allows authenticated users with Overall/Read access to access form validation endpoints
You are affected if the OpenShift Deployer plugin version is 1.2.0 or lower AND the plugin is installed in your Jenkins instance, since the missing permission check allows any authenticated user with basic read access to trigger SSRF attacks.
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 dataAdd a proper permission check (e.g., Permission check for Overall/Administer or a specific permission) to the doCheckLogin method to ensure only authorized users can trigger outbound connections from the Jenkins server.
Fix this in Openshift Deployer
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003081 — 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-1003081 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