dbcve.org
Artifact Repository ParameterApplication · Jenkins

CVE-2021-21622

MEDIUM · 5.4 CVSS v3.1 Published 2021-02-24
Fix available
A fix is available. Upgrade to after 1.0.0 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 Artifact Repository Parameter Plugin 1.0.0 and earlier does not escape parameter names and descriptions, 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 confidence

The Jenkins Artifact Repository Parameter Plugin versions 1.0.0 and earlier fail to properly escape parameter names and descriptions when rendering them in the UI, leading to a stored cross-site scripting (XSS) vulnerability. An attacker with Job/Configure permission can inject malicious JavaScript into these fields which will execute when other users view the configured parameters.

MitigationUpdate to a patched version of the Artifact Repository Parameter Plugin that properly escapes HTML characters in parameter names and descriptions, or remove the plugin if not required.

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
Artifact Repository ParameterApplication
Affected:<= 1.0.0

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. List installed Jenkins plugins
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the API: GET /pluginManager/plugins (requires admin). Look for 'Artifact Repository Parameter' in the list.
    Affected if The plugin is installed and its version is 1.0.0 or earlier (version column shows 1.0.0 or no version listed, indicating very early version).
  2. Check plugin version details
    In Manage Jenkins > Manage Plugins > Installed, find 'Artifact Repository Parameter' and check the Version column. If the version is not visible, check the plugin's wiki or the plugins directory for the installed date as a version indicator.
    Affected if Version is 1.0.0 or earlier, or the plugin is present without a displayed version (indicating it is the original unpatched release).
  3. Identify jobs using the plugin
    Review job configurations: for each job, go to Configure > Parameters section. Look for parameter types provided by this plugin (typically labeled related to artifact repository or artifact selection). Check job XML config files in JENKINS_HOME/jobs/<jobname>/config.xml for 'artifactRepositoryParameter' references.
    Affected if Any job is configured with parameters from the Artifact Repository Parameter plugin.
  4. Audit Job/Configure permission assignments
    Go to Manage Jenkins > Manage Users and check which users/groups have Overall/Read and Job/Configure permissions. In matrix-based security or project-based authorization, review the 'Job/Configure' permission column in the security matrix.
    Affected if Non-admin users or groups have Job/Configure permission, allowing them to configure jobs and inject malicious script into parameter fields.

You are affected if the Artifact Repository Parameter plugin is installed at version 1.0.0 or earlier AND any user with Job/Configure permission has configured a job using this plugin's parameters.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.0
Interim mitigation

Update to a patched version of the Artifact Repository Parameter Plugin that properly escapes HTML characters in parameter names and descriptions, or remove the plugin if not required.

Fix this in Artifact Repository Parameter Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21622 — 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-2021-21622 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