dbcve.org
Alauda Devops PipelineApplication · Jenkins

CVE-2019-16574

MEDIUM · 6.5 CVSS v3.1 Published 2019-12-17
Fix available
A fix is available. Upgrade to after 2.3.2 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Alauda DevOps Pipeline Plugin 2.3.2 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing 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

A missing permission check in Jenkins Alauda DevOps Pipeline Plugin 2.3.2 and earlier allows users with only Overall/Read permission to configure the plugin to connect to attacker-controlled URLs using credential IDs they specify. This enables theft of Jenkins-stored credentials by exploiting the plugin's credential lookup functionality without proper authorization checks.

MitigationUpgrade the Alauda DevOps Pipeline Plugin to a version beyond 2.3.2 that includes the permission check fix, or restrict Overall/Read access if upgrade is not possible.

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 Devops PipelineApplication
Affected:<= 2.3.2

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check if Alauda DevOps Pipeline plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin directory (typically $JENKINS_HOME/plugins/) for a folder named 'alauda-devops-pipeline' or similar
    Affected if The plugin folder or entry exists in the Jenkins plugin management interface
  2. Identify the installed version of the Alauda plugin
    In Jenkins > Manage Jenkins > Manage Plugins > Installed, find the Alauda DevOps Pipeline entry and note the Version column; alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin .hpi file
    Affected if The version is 2.3.2 or any version earlier than 2.3.2
  3. Verify if Overall/Read permission is granted to non-admin users
    Navigate to Jenkins > Manage Jenkins > Configure Global Security > Authorization, or check Manage Jenkins > Manage Users and their individual permission configurations; look for any user or group granted the Overall/Read permission
    Affected if Any user account (other than administrators) has Overall/Read permission enabled in the authorization matrix or security realm
  4. Confirm the plugin configuration is accessible to read-permission users
    Access the plugin configuration at Jenkins > Manage Jenkins > Configure System and locate the Alauda DevOps Pipeline configuration section, or check if a direct URL like /plugin/alauda-devops-pipeline/ is reachable
    Affected if Users with only Overall/Read permission can view or access the plugin's configuration page to input credential IDs or URLs
  5. Check for credential usage in plugin configuration
    Inspect the Alauda plugin configuration for stored credential IDs or configured Alauda service URLs; look for fields labeled 'Credentials', 'Credential ID', or similar that accept credential references
    Affected if The plugin configuration page contains credential ID fields or URL fields that can be modified by low-privilege users

You are affected if the Alauda DevOps Pipeline plugin version is 2.3.2 or earlier AND any user has Overall/Read permission (the minimum permission level) which would allow them to access the plugin's credential configuration and potentially exfiltrate stored credentials.

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

Upgrade the Alauda DevOps Pipeline Plugin to a version beyond 2.3.2 that includes the permission check fix, or restrict Overall/Read access if upgrade is not possible.

Fix this in Alauda Devops Pipeline Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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