Extended Choice ParameterApplication · Jenkins
CVE-2022-27204
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 vulnerability in Jenkins Extended Choice Parameter Plugin 346.vd87693c5a_86c 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 confidenceA CSRF vulnerability in Jenkins Extended Choice Parameter Plugin version 346.vd87693c5a_86c and earlier allows authenticated attackers to trick the Jenkins server into making outbound connections to attacker-specified URLs by leveraging the lack of proper CSRF token validation on certain endpoints.
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
Extended Choice ParameterApplication
<= 346.vd87693c5a_86cCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify Extended Choice Parameter plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins. Click on the 'Installed' tab and search for 'Extended Choice Parameter' in the list of installed plugins.Affected if The plugin appears in the installed plugins list
-
Check installed plugin versionOn the Installed plugins page, locate 'Extended Choice Parameter' and note the Version column. Compare this version number against 346.vd87693c5a_86c (versions 346.vd87693c5a_86c and earlier are affected).Affected if The installed version is 346.vd87693c5a_86c or any earlier version number
-
Verify Jenkins CSRF protection statusNavigate to Manage Jenkins > Configure Global Security. Locate the 'CSRF Protection' section under the Security header. Check if CSRF protection is enabled (the checkbox should be checked or the setting should show enabled).Affected if CSRF protection is disabled or not properly configured in Jenkins global security settings
A user is affected if the Extended Choice Parameter plugin is installed at version 346.vd87693c5a_86c or earlier AND CSRF protection is disabled or misconfigured in Jenkins, allowing the CSRF vulnerability to be exploited.
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 the Extended Choice Parameter Plugin to the latest patched version and ensure global Jenkins CSRF protection is enabled. Verify plugin functionality after updating.
Fix this in Extended Choice Parameter
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing3.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27204 — 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-27204 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