Agent Server ParameterApplication · Jenkins
CVE-2022-34183
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 Agent Server Parameter Plugin 1.1 and earlier does not escape the name and description of Agent Server 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 Agent Server Parameter Plugin versions 1.1 and earlier fails to properly escape the name and description fields of Agent Server parameters when rendering them in views. This stored XSS vulnerability allows an attacker with Item/Configure permission to inject malicious JavaScript that executes in the browsers of other users who view the affected parameter displays.
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
Agent Server ParameterApplication
<= 1.1CVSS 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 the Agent Server Parameter plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Agent Server Parameter' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Check the installed version of the pluginIn the same plugin management screen, locate the Agent Server Parameter plugin and note the version number shown in the 'Version' columnAffected if The version is 1.1 or any version lower than 1.1
-
Identify jobs using Agent Server ParameterNavigate to each job configuration screen (Job > Configure) and look for a section named 'Agent Server Parameter' under the 'Parameters' section. Alternatively, use the Jenkins script console with: Jenkins.instance.allItems.each { job -> if (job.hasProperty('parametersDefinition') && job.parametersDefinition.properties.any { it.class.name.contains('AgentServerParameter') }) { println job.fullName } }Affected if Any job is found with Agent Server Parameter definitions configured
-
Inspect parameter names and descriptions for suspicious contentFor each job with Agent Server Parameter, examine the 'Name' and 'Description' fields in the parameter configuration. Look for HTML tags, script tags, or JavaScript code (e.g., <script>, javascript:, onload, onerror, event handlers)Affected if Any parameter name or description contains HTML, JavaScript, or encoded script content
You are affected if the Jenkins Agent Server Parameter plugin version 1.1 or lower is installed AND any job has Agent Server Parameters configured with potentially malicious content in the name or description fields
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 to a patched version of the plugin when available. Until then, strictly limit Item/Configure permission to trusted users only and audit existing job configurations for suspicious parameter entries.
Fix this in Agent Server Parameter
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34183 — 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-34183 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