dbcve.org
Self Organizing Swarm ModulesPlugin / extension · Jenkins

CVE-2019-10309

CRITICAL · 9.3 CVSS v3.0 Published 2019-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
No privileges Zero-click

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 Self-Organizing Swarm Plug-in Modules Plugin clients that use UDP broadcasts to discover Jenkins masters do not prevent XML External Entity processing when processing the responses, allowing unauthorized attackers on the same network to read arbitrary files from Swarm clients.

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 Swarm Plug-in client uses UDP broadcasts for master discovery and processes XML responses without disabling external entity processing, allowing XXE injection. An attacker on the same network can send malicious XML responses to read arbitrary files from the client machine.

MitigationUpgrade to a patched version of the Swarm plugin that disables external entity processing in XML parsing, or disable UDP broadcast discovery and use explicit configuration instead.

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
Self Organizing Swarm ModulesPlugin / extension
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:H

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 Jenkins Swarm Plugin installation
    Identify if the Swarm client plugin/module is installed by checking for swarm-related JAR files, plugin directories, or running processes (e.g., swarm-client.jar or 'swarm' in process list)
    Affected if The Swarm plugin is present on the system
  2. Verify UDP broadcast discovery is enabled
    Check the Swarm client configuration or startup parameters for UDP broadcast settings. Look for discovery mechanisms that use UDP port 9000 (default Swarm discovery port) or broadcast-based discovery. Review startup scripts or config files for 'udp', 'broadcast', or 'discovery' flags set to enabled.
    Affected if UDP broadcast-based master discovery is enabled in the Swarm client configuration
  3. Assess network exposure of UDP discovery port
    Examine network configuration to determine if the UDP discovery port (typically 9000) is accessible from untrusted network segments. Check firewall rules, network ACLs, and whether the client is on a shared or untrusted network (e.g., corporate LAN, public WiFi) where unauthorized parties could send packets.
    Affected if The UDP discovery port is reachable from untrusted network locations or the client operates on a network with untrusted adjacent systems
  4. Confirm XML parsing lacks XXE protection
    Review the Swarm plugin version and its XML parser configuration. Since all versions are affected, verify whether external entity processing has been explicitly disabled in XML parsing. This typically requires code review or checking if the installed version predates the security fix.
    Affected if The XML parser does not have external entity (XXE) protection explicitly disabled

A user is affected if the Swarm plugin is installed, UDP broadcast discovery is enabled, and the UDP discovery port is accessible to untrusted attackers on the same network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the Swarm plugin that disables external entity processing in XML parsing, or disable UDP broadcast discovery and use explicit configuration instead.

Fix this in Self Organizing Swarm Modules Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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