dbcve.org
Maven MetadataApplication · Jenkins

CVE-2022-36905

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to after 2.2 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 Maven Metadata Plugin for Jenkins CI server Plugin 2.2 and earlier does not perform URL validation for the Repository Base URL of List maven artifact versions 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

The Maven Metadata Plugin for Jenkins versions 2.2 and earlier lacks URL validation for the Repository Base URL field in 'List maven artifact versions' parameters, allowing stored XSS. Attackers with Item/Configure permission can inject malicious scripts that execute in other users' browsers when viewing the configuration.

MitigationUpgrade to Maven Metadata Plugin version 2.3 or later which implements proper URL validation, or restrict Item/Configure permissions to trusted users until the patch is applied.

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
Maven MetadataApplication
Affected:<= 2.2

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. Confirm Maven Metadata Plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Maven Metadata' in the list of installed plugins. Note the version number displayed.
    Affected if The plugin appears in the installed plugins list with a version number.
  2. Check plugin version against affected range
    Compare the installed Maven Metadata Plugin version to the affected range: version 2.2 or earlier.
    Affected if The installed version is 2.2 or earlier.
  3. Identify jobs using List maven artifact versions parameter
    Navigate to Jenkins > Manage Jenkins > Script Console and run: Jenkins.instance.allItems.each { job -> job.parametersDefinitionList.each { param -> if (param.typeName == 'ListMavenArtifactVersions' || param.toString().contains('ListMavenArtifactVersions')) { println job.fullName } } }
    Affected if One or more jobs are found using the ListMavenArtifactVersions parameter.
  4. Inspect Repository Base URL configuration in affected jobs
    For each identified job, go to the job configuration page, find the 'List maven artifact versions' parameter, and examine the 'Repository Base URL' field for any injected script tags, javascript: URLs, or unusual characters.
    Affected if The Repository Base URL field contains suspicious content such as <script>, javascript:, or other XSS payloads.
  5. Review recent configuration changes
    Click on the job, go to 'Configuration History' or check the audit log for recent changes to the parameter configuration, looking for modifications from untrusted users.
    Affected if Configuration was recently modified by a user who should not have Item/Configure permission.

A user is affected if the Maven Metadata Plugin version is 2.2 or earlier AND at least one job contains a 'List maven artifact versions' parameter with a Repository Base URL containing unvalidated or malicious content.

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 2.2
Interim mitigation

Upgrade to Maven Metadata Plugin version 2.3 or later which implements proper URL validation, or restrict Item/Configure permissions to trusted users until the patch is applied.

Recommended fix Moderate confidence

Maven Metadata Plugin version > 2.2 (check Jenkins plugin repository for latest available version)

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the 'Installed' tab
  3. 3. Locate the 'Maven Metadata' plugin in the list
  4. 4. If an update is available, click 'Update' to upgrade to the latest version
  5. 5. Restart Jenkins if required to complete the update
  6. 6. After updating, verify the Maven Metadata plugin version is greater than 2.2

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

Fix this in Maven Metadata Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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