Alauda Kubernetes SupportApplication · Jenkins

CVE-2019-16575

HIGH · 8.8 CVSS v3.1 Published 2019-12-17
Fix available
A fix is available. Upgrade to after 2.3.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 cross-site request forgery vulnerability in Jenkins Alauda Kubernetes Suport Plugin 2.3.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing the Kubernetes service account token or credentials stored in Jenkins.

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

Cross-site request forgery (CSRF) vulnerability in Jenkins Alauda Kubernetes Support Plugin version 2.3.0 and earlier allows remote attackers to trigger authenticated requests to attacker-specified URLs using stored credential IDs, potentially exfiltrating Kubernetes service account tokens or other Jenkins credentials stored in the system.

MitigationUpdate the Alauda Kubernetes Support Plugin to a version newer than 2.3.0 that addresses this CSRF vulnerability. If no patched version is available, disable the plugin and review all stored credentials for potential compromise.

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
Alauda Kubernetes SupportApplication
Affected:<= 2.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if Alauda Kubernetes Support Plugin is installed
    Navigate to Jenkins Manage Plugins > Installed tab and search for 'Alauda Kubernetes Support', or check the plugin directory if you have direct filesystem access
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed version of the plugin
    In Jenkins, go to Manage Plugins > Installed and locate the Alauda Kubernetes Support Plugin to view its version number, then compare against the affected range of 2.3.0 and earlier
    Affected if The displayed version is 2.3.0 or any earlier version
  3. Verify the plugin is enabled and active
    Check the Jenkins configuration under Manage Jenkins > Configure System or Manage Jenkins > Global Security to see if the Alauda Kubernetes Support plugin features are currently enabled
    Affected if The plugin is installed, vulnerable version, and actively loaded by Jenkins
  4. Check for stored credential usage
    Review Jenkins credentials configuration under Manage Jenkins > Credentials to see if any Kubernetes-related credentials or service account tokens are stored, particularly those associated with Alauda or Kubernetes cloud configurations
    Affected if Any Kubernetes service account tokens or other Jenkins credentials are stored in the system while the vulnerable plugin version is present

You are affected if the Alauda Kubernetes Support Plugin is installed with version 2.3.0 or earlier and the plugin is enabled, regardless of whether credentials are actively configured.

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 2.3.0
Interim mitigation

Update the Alauda Kubernetes Support Plugin to a version newer than 2.3.0 that addresses this CSRF vulnerability. If no patched version is available, disable the plugin and review all stored credentials for potential compromise.

Fix this in Alauda Kubernetes Support Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.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-2019-16575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-16575 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