Openshift DeployerApplication · Jenkins
CVE-2022-36909
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 1.2.0 and earlier allows attackers with Overall/Read permission 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 confidenceThe Jenkins OpenShift Deployer Plugin 1.2.0 and earlier lacks permission checks on certain endpoints, allowing any user with Overall/Read permission to probe for file existence on the Jenkins controller filesystem and to exfiltrate SSH key files to attacker-controlled URLs. This is a classic missing authorization check vulnerability where the plugin fails to enforce appropriate access controls on file operations.
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 Jenkins > Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i openshiftAffected if The OpenShift Deployer plugin appears in the installed plugins list
-
Check installed plugin versionIn Manage Plugins > Installed, find the OpenShift Deployer plugin and note the version number shown in the version columnAffected if The version is 1.2.0 or earlier
-
Review users with Overall/Read permissionNavigate to Jenkins > Manage Jenkins > Manage Users, then check Matrix Authorization Strategy under Manage Jenkins > Configure Global Security to see which users or groups have Overall/Read permissionAffected if Any untrusted or anonymous users have Overall/Read permission enabled
-
Audit plugin configuration for SSH key pathsInspect the OpenShift Deployer plugin configuration at Jenkins > Manage Jenkins > Configure System > OpenShift Deployer, looking for configured SSH key file pathsAffected if SSH key file paths are configured and the plugin version is vulnerable
-
Check for suspicious outbound network behaviorReview Jenkins controller logs and network traffic for connections from Jenkins to unexpected external IP addresses or URLs, which could indicate exfiltration attemptsAffected if Outbound connections to unknown external URLs are observed in logs or network logs
A user is affected if the OpenShift Deployer plugin version is 1.2.0 or earlier AND untrusted users have Overall/Read permission enabled in Jenkins.
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 dataUpgrade to OpenShift Deployer Plugin version 1.3.0 or later which implements proper permission checks. Until then, restrict Overall/Read permission to only trusted users and consider disabling the plugin if not needed.
Fix this in Openshift Deployer
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36909 — 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-2022-36909 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