RecipeApplication · Jenkins
CVE-2022-34792
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 Recipe Plugin 1.2 and earlier allows attackers to send an HTTP request to an attacker-specified URL and parse the response as XML.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Recipe Plugin versions 1.2 and earlier allows authenticated or unauthenticated attackers to trick users into sending HTTP requests to attacker-specified URLs, with the response being parsed as XML.
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
RecipeApplication
<= 1.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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.
-
Check if Jenkins Recipe Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the plugin directory on the Jenkins master (typically $JENKINS_HOME/plugins/) for a folder named 'recipe' or 'jenkins-recipe-plugin'Affected if The plugin is not present in the installed plugins list or plugin directory
-
Identify the installed version of Jenkins Recipe PluginIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate 'Recipe' in the list to see the version column, or inspect the plugin's MANIFEST.MF file in $JENKINS_HOME/plugins/recipe/WEB-INF/Affected if The version is 1.2 or earlier (the vulnerable versions)
-
Confirm the plugin is enabled and loadedCheck the Jenkins > Manage Jenkins > Manage Plugins > Installed tab to verify the plugin status shows as 'Enabled' or check /pluginManager/plugin/{recipe}/status via Jenkins CLI or APIAffected if The plugin is enabled and loaded into the Jenkins runtime
A user is affected if the Jenkins Recipe Plugin is installed, enabled, and running at version 1.2 or earlier.
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.
dbcve · scopedUpdate the Jenkins Recipe Plugin to a version newer than 1.2 that includes the CSRF fix, or disable the plugin if not needed.
Recipe Plugin version greater than 1.2 (check Jenkins security advisory for exact fixed version)
- Check Jenkins Recipe Plugin releases on the Jenkins plugin repository or Jenkins security advisory for CVE-2022-34792 to confirm the fixed version
- Navigate to Manage Jenkins > Manage Plugins > Available tab
- Locate the Recipe plugin in the list
- If a newer version than 1.2 is available, select it and click 'Download now and install after restart'
- After installation, restart Jenkins or wait for the scheduled restart
- Verify the new version is installed by going to Manage Jenkins > Manage Plugins > Installed tab and checking the Recipe plugin version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Recipe
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34792 — 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-34792 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