dbcve.org
Maven Repository ServerApplication · Jenkins

CVE-2023-35144

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 project and build display names on the Build Artifacts As Maven Repository page, resulting in a stored cross-site scripting (XSS) vulnerability.

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 does not escape project and build display names on the Build Artifacts As Maven Repository page, resulting in a stored cross-site scripting (XSS) vulnerability. An attacker who can set project or build display names can inject malicious JavaScript that executes when other users view this page.

MitigationUpgrade Jenkins Maven Repository Server Plugin to version 1.11 or later which implements proper escaping of project and build display names.

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. Verify Maven Repository Server Plugin is installed
    Go to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Maven Repository Server' or check the plugin directory $JENKINS_HOME/plugins for maven-repository-plugin or similar.
    Affected if The plugin is not found in the installed plugins list, then this CVE does not apply.
  2. Identify the installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Maven Repository Server plugin and note the Version column. Alternatively, check the plugin's manifest file (MANIFEST.MF) in $JENKINS_HOME/plugins/maven-repository-plugin/ or check the plugin's changelog.
    Affected if The installed version is 1.10 or earlier.
  3. Confirm user has permission to set display names
    Verify if the user or attacker has Configure permission on jobs. This can be checked in Jenkins > Manage Jenkins > Manage and Assign Roles. The XSS requires an attacker to set project or build display names, which typically requires Job/Configure permission.
    Affected if Users with limited permissions (only read access) cannot inject the payload, but administrators or users with job configure rights can.
  4. Check if Build Artifacts As Maven Repository is in use
    Navigate to a job's 'Build Artifacts As Maven Repository' page (typically at /maven-repository-plugin/artifact/ of a job). This page displays project and build names unsafely if vulnerable.
    Affected if This page is accessible and displays unsanitized project/build names.

You are affected if the Maven Repository Server Plugin version 1.10 or earlier is installed and users with job configuration permissions can access the Build Artifacts As Maven Repository page.

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 Jenkins Maven Repository Server Plugin to version 1.11 or later which implements proper escaping of project and build display names.

Recommended fix High confidence

Maven Repository Server Plugin version 1.11

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Select the 'Installed' tab
  3. Locate 'Maven Repository Server' plugin in the list
  4. If an update is available, select it and click 'Download now and install after restart'
  5. After the update completes, verify the plugin version is 1.11 or higher

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

Fix this in Maven Repository Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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