dbcve.org
Openshift DeployerApplication · Jenkins

CVE-2022-36908

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 check for the existence of an attacker-specified file path on the Jenkins controller file system and to upload a SSH key file from the Jenkins controller file system to an attacker-specified URL.

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

This is a CSRF vulnerability in the Jenkins OpenShift Deployer Plugin versions 1.2.0 and earlier. Attackers can exploit this to check for existence of arbitrary file paths on the Jenkins controller file system and to exfiltrate SSH key files from the Jenkins controller to attacker-specified URLs. The vulnerability allows unauthorized file system access and sensitive data theft without direct authentication, relying on tricking authenticated users into triggering malicious requests.

MitigationUpgrade the OpenShift Deployer Plugin to version 1.2.1 or later, which includes CSRF protection tokens (crumbs). Until upgraded, monitor Jenkins logs for suspicious file access patterns and restrict user permissions to the minimum required.

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. Identify OpenShift Deployer Plugin installation and version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed. Search for 'OpenShift Deployer' or 'openshift-deployer' in the plugin list and note the Version column.
    Affected if The plugin is installed and the version is 1.2.0 or earlier.
  2. Verify Jenkins CSRF protection is enabled
    Navigate to Jenkins > Manage Jenkins > Configure Global Security. Under the 'CSRF Protection' section, confirm that 'Enable proxy compatibility' or 'Enable UUID crumb validation' is checked and that a valid Crumb Issuer is configured.
    Affected if CSRF protection is disabled or not properly configured.
  3. Review Jenkins access logs for file access patterns
    Examine Jenkins logs (Jenkins > Manage Jenkins > System Log > All Jenkins Logs) or the jenkins.log file for unusual GET requests to file paths, especially looking for patterns like '/adjuncts/' or requests containing file extensions such as '.pem', '.key', or '.ssh'.
    Affected if Log entries show unusual file path access attempts or requests to unknown external URLs.
  4. Audit outbound HTTP requests from Jenkins
    Check network logs, proxy logs, or firewall logs for outbound HTTP/HTTPS requests initiated by the Jenkins process to unfamiliar or attacker-controlled URLs, particularly those containing '/adjuncts/' or file paths.
    Affected if Jenkins has made outbound requests to unknown URLs, especially those resembling file exfiltration patterns.

A user is affected if the OpenShift Deployer Plugin version 1.2.0 or earlier is installed and CSRF protection is disabled or bypassed, allowing unauthorized file system access to occur.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.0
Interim mitigation

Upgrade the OpenShift Deployer Plugin to version 1.2.1 or later, which includes CSRF protection tokens (crumbs). Until upgraded, monitor Jenkins logs for suspicious file access patterns and restrict user permissions to the minimum required.

Recommended fix High confidence

1.2.1 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the OpenShift Deployer plugin in the list
  5. If the current version is 1.2.0 or earlier, click 'Update' to upgrade to the latest version
  6. Restart Jenkins if required to complete the installation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Deployer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-36908 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