dbcve.org
Package VersionApplication · Jenkins

CVE-2022-34193

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Jenkins Package Version Plugin 1.0.1 and earlier does not escape the name of Package version 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 confidence

Jenkins Package Version Plugin 1.0.1 and earlier fails to escape Package version parameter names when rendering them in views, allowing stored XSS injection. Attackers with Item/Configure permission can embed malicious JavaScript into parameter names that executes when other users view the parameter display.

MitigationUpdate to a patched version of the Package Version Plugin when available; otherwise, restrict Item/Configure permission to trusted users only and validate/sanitize all parameter name inputs.

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
Package VersionApplication
Affected:<= 1.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Package Version Plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed tab, search for 'Package Version' in the filter, and confirm the plugin appears in the list.
    Affected if The plugin is present in the installed plugins list.
  2. Determine the installed version of Package Version Plugin
    In the same plugin list view, note the Version column value displayed next to the Package Version plugin entry.
    Affected if The version is 1.0.1 or earlier.
  3. Identify jobs using Package Version plugin parameters
    Review job configurations: for each job, go to Configure > Build Steps > Package Version section (if present), and inspect any defined Package version parameters and their Name fields.
    Affected if Jobs contain Package version parameters with names that could have been supplied by untrusted users.
  4. Audit Item/Configure permission assignments
    Go to Manage Jenkins > Manage and Assign Roles > Manage Roles (or your configured authorization matrix), and review which users or groups are granted the Item/Configure permission.
    Affected if Users with Item/Configure permission are untrusted or include members outside your security boundary.

You are affected if the Package Version Plugin version is 1.0.1 or earlier AND any job using the plugin exposes parameter names that could have been crafted by users with Item/Configure permission.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.0.1
Interim mitigation

Update to a patched version of the Package Version Plugin when available; otherwise, restrict Item/Configure permission to trusted users only and validate/sanitize all parameter name inputs.

Recommended fix Moderate confidence

Package Version Plugin 1.0.2

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Search for 'Package Version' plugin
  4. 4. If an update is available, select the plugin and click 'Update'
  5. 5. After updating, restart Jenkins if required
  6. 6. Verify the plugin version is 1.0.2 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Package Version Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34193 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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