dbcve.org
Docker SwarmApplication · Jenkins

CVE-2023-40350

MEDIUM · 5.4 CVSS v3.1 Published 2023-08-16
Fix available
A fix is available. Upgrade to after 1.11 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 Docker Swarm Plugin 1.11 and earlier does not escape values returned from Docker before inserting them into the Docker Swarm Dashboard view, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control responses from Docker.

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 · moderate confidence

The Jenkins Docker Swarm Plugin 1.11 and earlier does not escape values returned from Docker API responses before rendering them in the Docker Swarm Dashboard view, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers who can control Docker responses (e.g., by compromising the Docker daemon or man-in-the-middle attacks) can inject malicious scripts that execute in the browsers of users viewing the dashboard.

MitigationUpgrade to a patched version of the Docker Swarm Plugin (latest version recommended). If immediate patching is not feasible, restrict network access between Jenkins and Docker to trusted sources, and ensure Docker responses cannot be controlled by untrusted parties.

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
Docker SwarmApplication
Affected:<= 1.11

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 Docker Swarm Plugin is installed
    In Jenkins, navigate to Manage Jenkins > Manage Plugins > Installed tab. Search for 'Docker Swarm Plugin' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list.
  2. Check the installed version
    In the same plugin list view, locate the Docker Swarm Plugin and note its version number displayed in the version column.
    Affected if The version is 1.11 or any version earlier than 1.11.
  3. Verify Docker Swarm configuration exists
    Navigate to Manage Jenkins > System > Docker Swarm section or look for Docker Swarm configuration under Jenkins > System. Check if any Docker daemon connections are configured.
    Affected if Any Docker Swarm configuration is saved and active in Jenkins.
  4. Confirm Docker Swarm Dashboard is accessible
    Access the Jenkins main page and look for the Docker Swarm Dashboard link in the left navigation panel, or navigate directly to the Docker Swarm view if it exists for your build jobs.
    Affected if The Docker Swarm Dashboard view is present and accessible to users.

If the Docker Swarm Plugin version 1.11 or earlier is installed, a Docker Swarm configuration exists, and users can access the Docker Swarm Dashboard, then the environment is affected by this stored XSS vulnerability.

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

Upgrade to a patched version of the Docker Swarm Plugin (latest version recommended). If immediate patching is not feasible, restrict network access between Jenkins and Docker to trusted sources, and ensure Docker responses cannot be controlled by untrusted parties.

Recommended fix Moderate confidence

Docker Swarm Plugin 1.12

  1. Upgrade Jenkins Docker Swarm Plugin from version 1.11 or earlier to version 1.12 or later

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

Fix this in Docker Swarm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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