Openshift DeployerApplication · Jenkins

CVE-2022-36906

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to after 1.2.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins OpenShift Deployer Plugin 1.2.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified username and password.

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 confidence

A CSRF vulnerability in Jenkins OpenShift Deployer Plugin 1.2.0 and earlier allows attackers to trick authenticated users into making unintended requests that connect to attacker-specified URLs using attacker-specified credentials, effectively enabling unauthorized external connections through the victim's authenticated session.

MitigationUpgrade to Jenkins OpenShift Deployer Plugin version 1.2.1 or later, which includes CSRF protection fixes. Alternatively, disable the plugin if not needed until an upgrade is possible.

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
Affected:<= 1.2.0

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify OpenShift Deployer plugin is installed
    Log into Jenkins and navigate to Manage Jenkins > Manage Plugins > Installed tab, or list the contents of $JENKINS_HOME/plugins/ directory for a folder named openshift-deployer or similar
    Affected if The OpenShift Deployer plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In Jenkins UI, click on the OpenShift Deployer plugin entry to view its details, or inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin hpi/jpi file
    Affected if The displayed version is 1.2.0 or earlier
  3. Confirm the plugin is actively configured
    Navigate to the Jenkins configuration pages related to OpenShift (typically under Manage Jenkins or job configurations) to see if any OpenShift Deployer configurations exist
    Affected if The plugin has active configurations, jobs, or credentials defined using it
  4. Check if CSRF protection is enabled globally
    Go to Manage Jenkins > Configure Global Security and verify the CSRF Protection setting; note that plugin-specific CSRF protection is what matters for this CVE, and earlier plugin versions lack it
    Affected if CSRF protection is not enforced at the Jenkins level or the plugin version lacks built-in CSRF protection (versions 1.2.0 and earlier)
  5. Identify any authenticated sessions or credentials in use
    Review Manage Credentials pages and any OpenShift-related job configurations to see if credentials are stored and used with the plugin
    Affected if Any credentials are configured for use with the OpenShift Deployer plugin

The environment is affected if the Jenkins OpenShift Deployer plugin is installed and its version is 1.2.0 or earlier, regardless of whether it is actively configured or in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.2.0
Interim mitigation

Upgrade to Jenkins OpenShift Deployer Plugin version 1.2.1 or later, which includes CSRF protection fixes. Alternatively, disable the plugin if not needed until an upgrade is possible.

Fix this in Openshift Deployer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36906 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36906 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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