dbcve.org
Maven Repository ServerApplication · Jenkins

CVE-2023-35143

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to after 1.10 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 Repository Server Plugin 1.10 and earlier does not escape the versions of build artifacts on the Build Artifacts As Maven Repository page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control maven project versions in `pom.xml`.

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 Maven Repository Server Plugin versions 1.10 and earlier fails to escape build artifact versions on the 'Build Artifacts As Maven Repository' page, creating a stored XSS vulnerability. Attackers with control over Maven project versions in pom.xml can inject malicious scripts that execute when users view the affected page.

MitigationUpgrade to Maven Repository Server Plugin version 1.11 or later which includes proper escaping of artifact versions. Alternatively, restrict permissions to modify pom.xml versions to trusted users only.

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 Repository ServerApplication
Affected:<= 1.10

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. Check if Maven Repository Server Plugin is installed
    Navigate to Manage Jenkins -> Manage Plugins -> Installed and search for 'Maven Repository Server' in the list of installed plugins
    Affected if Plugin is not installed or not present in the plugin list
  2. Verify the installed plugin version
    In the installed plugins list, find 'Maven Repository Server' and note the version column. Compare this version to the affected range: versions 1.10 and earlier are vulnerable
    Affected if Installed version is 1.10 or earlier
  3. Check if the Build Artifacts As Maven Repository feature is accessible
    Look for a job or view that uses 'Build Artifacts As Maven Repository' functionality - typically found as a build step or a configured view in Maven-based jobs
    Affected if The feature is configured and accessible in any Jenkins job or view
  4. Identify if untrusted users can modify pom.xml versions
    Review job configurations for Maven jobs and check if users with limited permissions (such as Maven Release Plugin users or those who can edit pom.xml) have the ability to modify project versions in pom.xml files
    Affected if Users with permissions to edit or trigger builds that modify Maven project versions exist in the environment

A user is affected if the Maven Repository Server Plugin version 1.10 or earlier is installed AND the Build Artifacts As Maven Repository feature is in use, allowing potential injection through Maven pom.xml version fields.

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.10
Interim mitigation

Upgrade to Maven Repository Server Plugin version 1.11 or later which includes proper escaping of artifact versions. Alternatively, restrict permissions to modify pom.xml versions to trusted users only.

Recommended fix High confidence

Maven Repository Server Plugin version 1.11 or later

  1. In Jenkins, go to Manage Jenkins > Manage Plugins
  2. Navigate to the 'Installed' tab
  3. Locate 'Maven Repository Server' in the list
  4. If an update is available, select the plugin and click 'Download now and install after restart'
  5. Alternatively, manually download the updated .hpi file from the Jenkins Plugin Repository and upload it via 'Advanced' > 'Upload Plugin'
  6. Restart Jenkins to complete the installation
  7. Verify the plugin shows version 1.11 or later in the installed plugins list

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

Fix this in Maven Repository Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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