Openshift DeployerApplication · Jenkins
CVE-2022-36907
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 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 confidenceThe Jenkins OpenShift Deployer Plugin versions 1.2.0 and earlier lacks a permission check before allowing HTTP connections to arbitrary URLs. Attackers with only Overall/Read permission (the baseline read access in Jenkins) can configure the plugin to connect to any attacker-specified URL using attacker-specified credentials.
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, or inspect $JENKINS_HOME/plugins/ for openshift-deployer directoryAffected if The plugin directory or entry exists in Jenkins plugin management
-
Check installed plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate OpenShift Deployer in the list to view the version column; alternatively, inspect the plugin's MANIFEST.MF or .jpi fileAffected if The displayed version is 1.2.0 or earlier
-
Check if plugin has active configurationNavigate to the plugin configuration page (typically under Manage Jenkins or project configuration) and examine whether any HTTP endpoint, credentials, or connection settings have been savedAffected if Configuration data exists (credential entries, URLs, or connection profiles are saved)
-
Verify current permission model on plugin configurationAttempt to access the plugin configuration page and check whether Overall/Read permission alone is sufficient to modify or save settings, or whether higher privileges (Overall/Administer) are requiredAffected if Users with only Overall/Read permission can access and modify the plugin's HTTP connection or credential configuration settings
A user is affected if the OpenShift Deployer Plugin version is 1.2.0 or earlier AND the plugin has configuration saved AND users with only Overall/Read permission can access the configuration settings.
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 to Jenkins OpenShift Deployer Plugin version 1.3.0 or later, which implements proper permission checks requiring higher privileges (Overall/Administer) for HTTP connection configuration.
Fix this in Openshift Deployer
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36907 — 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-36907 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