Openstack HeatApplication · Jenkins
CVE-2022-36911
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 cross-site request forgery (CSRF) vulnerability in Jenkins Openstack Heat Plugin 1.5 and earlier allows attackers to connect 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 confidenceThis is a CSRF vulnerability in the Jenkins Openstack Heat Plugin version 1.5 and earlier. The vulnerability allows attackers to trick authenticated Jenkins users into making requests that cause the Jenkins server to connect to attacker-controlled URLs, potentially enabling SSRF attacks or unauthorized network access.
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
Openstack HeatApplication
<= 1.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Openstack Heat Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and look for 'Openstack Heat' in the list, or query the Jenkins API endpoint /pluginManager/plugin/{plugin} to check if the plugin existsAffected if Plugin is not present in the installed plugins list
-
Check the installed plugin versionIn the Installed plugins tab, locate the Openstack Heat Plugin and note the Version column, or retrieve the version from the plugin manifest at JENKINS_HOME/plugins/openstack-heat/WEB-INF/manifest.jsonAffected if Version is 1.5 or lower (for example: 1.5, 1.4, 1.3, etc.)
-
Confirm the plugin is enabledCheck if Openstack Heat appears in Jenkins configuration (Manage Jenkins > System > look for Openstack Heat cloud configuration) or is used as a build step in any jobsAffected if Plugin configuration exists or is used in jobs, meaning it is actively processing requests
If the Openstack Heat Plugin version is 1.5 or earlier and the plugin is installed and enabled, the environment is vulnerable to CVE-2022-36911 CSRF 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 dataUpgrade the Jenkins Openstack Heat Plugin to version 1.6 or later, which should include proper CSRF protection (crumb) validation. If upgrading is not immediately possible, restrict Jenkins user permissions and network access to limit exposure.
Fix this in Openstack Heat
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36911 — 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-36911 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