Git ParameterApplication · Jenkins
CVE-2020-2238
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 · uneditedJenkins Git Parameter Plugin 0.9.12 and earlier does not escape the repository field on the 'Build with Parameters' page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Job/Configure permission.
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 confidenceJenkins Git Parameter Plugin versions 0.9.12 and earlier contain a stored cross-site scripting (XSS) vulnerability where the repository field on the 'Build with Parameters' page is not properly escaped. Attackers with Job/Configure permission can inject malicious JavaScript into the repository field, which executes when other users view the parameters page.
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
Git ParameterApplication
<= 0.9.12CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Git Parameter Plugin installationNavigate to Manage Jenkins > Manage Plugins > Installed tab and locate 'Git Parameter Plugin' in the list, or run: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i 'git-parameter'Affected if Plugin is not listed as installed
-
Determine installed version of Git Parameter PluginIn the Installed plugins tab, note the version displayed next to Git Parameter Plugin. Compare your version against 0.9.12Affected if Version is 0.9.12 or earlier
-
Identify jobs using Git Parameter PluginReview job configurations: select each job, go to Configure, and look for 'Git Parameter' or 'Parameter' type entries in the Parameters section. Check if any jobs use this pluginAffected if One or more jobs are configured with Git Parameter plugin
-
Inspect repository field values in affected jobsIn each job using Git Parameter Plugin, examine the repository field within the parameter configuration. Look for any script tags, javascript: URIs, or other suspicious contentAffected if Repository field contains executable script content
-
Review who has Job/Configure permission on vulnerable jobsNavigate to Manage Jenkins > Manage and Assign Users > Assign Roles, or check each job's permission settings to see which users or groups have Job/Configure permissionAffected if Users who are not fully trusted have Job/Configure permission on jobs using Git Parameter Plugin
Environment is affected if Git Parameter Plugin version 0.9.12 or earlier is installed AND there are jobs using this plugin where untrusted users have Job/Configure permission, allowing stored XSS injection into the repository field.
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 Git Parameter Plugin to a version that patches this vulnerability (0.9.13 or later). As a compensating control, restrict Job/Configure permission to only trusted users until the upgrade is applied.
Fix this in Git Parameter
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2238 — 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-2020-2238 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