dbcve.org
Jx ResourcesApplication · Jenkins

CVE-2019-10339

HIGH · 8.8 CVSS v3.1 Published 2019-06-11
Fix available
A fix is available. Upgrade to after 1.0.36 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
A missing permission check in Jenkins JX Resources Plugin 1.0.36 and earlier in GlobalPluginConfiguration#doValidateClient allowed users with Overall/Read access to have Jenkins connect to an attacker-specified Kubernetes server, potentially leaking credentials.

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

A missing permission check in Jenkins JX Resources Plugin versions 1.0.36 and earlier in the GlobalPluginConfiguration#doValidateClient method allows authenticated users with only Overall/Read access to configure Jenkins to connect to an attacker-specified Kubernetes server, potentially exposing credentials stored in Jenkins.

MitigationUpgrade JX Resources Plugin to a version after 1.0.36 that includes proper permission checks, or restrict Overall/Read access to untrusted users until the patch can be 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
Jx ResourcesApplication
Affected:<= 1.0.36

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check if JX Resources Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and look for 'JX Resources' or 'jx-resources' in the list of installed plugins
    Affected if The plugin is listed as installed in Jenkins
  2. Determine the installed version of JX Resources Plugin
    In the Installed plugins tab, find the Version column for the JX Resources plugin. Compare this version number to 1.0.36
    Affected if The installed version is 1.0.36 or earlier
  3. Check access to the vulnerable method
    Attempt to access or verify the existence of the GlobalPluginConfiguration#doValidateClient endpoint by examining plugin configuration URLs or checking if the 'Configure Clouds' or related Kubernetes configuration page is accessible
    Affected if The plugin configuration interface for Kubernetes resources is accessible without elevated permissions
  4. Identify users with Overall/Read permission
    Navigate to Jenkins > Manage Jenkins > Manage Users and review user accounts. Check Jenkins > Manage Jenkins > Configure Global Security to see which users are granted only the Overall/Read permission
    Affected if There are user accounts in Jenkins that have only Overall/Read access (no higher-level permissions)
  5. Verify credential storage
    Check if Kubernetes credentials or cloud configuration credentials are stored in Jenkins (look under Jenkins > Manage Jenkins > Configure Clouds or Credentials)
    Affected if Kubernetes or cloud credentials are stored in Jenkins that could be exposed if the attacker-controlled Kubernetes server connection succeeds

You are affected if the JX Resources Plugin version is 1.0.36 or earlier, the plugin is installed and accessible, and users with only Overall/Read permission exist in Jenkins with credentials stored that could be exposed to an attacker-specified Kubernetes server.

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
Upgrade available Upgrade to a release after 1.0.36
Interim mitigation

Upgrade JX Resources Plugin to a version after 1.0.36 that includes proper permission checks, or restrict Overall/Read access to untrusted users until the patch can be applied.

Fix this in Jx Resources Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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