Readonly ParameterApplication · Jenkins
CVE-2022-34194
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 Readonly Parameter Plugin 1.0.0 and earlier does not escape the name and description of Readonly String and Readonly Text parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/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 confidenceThe Jenkins Readonly Parameter Plugin versions 1.0.0 and earlier fails to escape the name and description fields of Readonly String and Readonly Text parameters when rendering them in parameter display views. This allows a stored XSS payload injected through these fields to execute in the browsers of users who view the affected parameter pages.
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
Readonly ParameterApplication
<= 1.0.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
- 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 Readonly Parameter Plugin is installedGo to Manage Jenkins > Manage Plugins > Installed and search for 'Readonly Parameter'. Note the version number displayed.Affected if The plugin is installed with version 1.0.0 or earlier (no version number or version <= 1.0.0 indicates vulnerability).
-
Identify jobs using Readonly String or Readonly Text parametersReview Jenkins jobs that use the Readonly Parameter plugin. For each job, go to Configure > Parameters section and identify if any parameters are of type 'Readonly String' or 'Readonly Text'.Affected if Jobs contain Readonly String or Readonly Text parameter definitions - these are the vulnerable parameter types.
-
Inspect parameter name and description fieldsIn the job configuration under Parameters, examine the 'Name' and 'Description' fields for any Readonly String or Readonly Text parameters. Check if these fields contain HTML, JavaScript, or special characters that could represent injected payloads.Affected if The name or description fields contain unsanitized user-controlled content, especially if sourced from untrusted external inputs or if the fields contain raw HTML/script tags.
-
View parameter display in build pagesNavigate to a completed build of an affected job and view the parameter display page (build with parameters). Right-click and inspect the page source to examine how the Readonly parameter name and description are rendered.Affected if The rendered HTML shows unescaped characters (e.g., <script> tags visible in source rather than <script>) indicating the XSS vulnerability is present and exploitable.
You are affected if the Readonly Parameter Plugin version is 1.0.0 or earlier AND you have jobs using Readonly String or Readonly Text parameters whose name/description fields may contain untrusted content.
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 Readonly Parameter Plugin to a version that properly escapes parameter name and description fields. Alternatively, restrict Item/Configure permission to trusted administrators only until a patch is available.
Fix this in Readonly Parameter
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34194 — 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-34194 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