dbcve.org
Azure AdApplication · Jenkins

CVE-2020-2119

MEDIUM · 5.3 CVSS v3.1 Published 2020-02-12
Fix available
A fix is available. Upgrade to after 1.1.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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 Azure AD Plugin 1.1.2 and earlier transmits configured credentials in plain text as part of the global Jenkins configuration form, potentially resulting in their exposure.

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

Jenkins Azure AD Plugin 1.1.2 and earlier transmits configured Azure AD credentials in plain text as part of the global Jenkins configuration form submission, allowing them to be exposed in transit or logs.

MitigationUpdate Jenkins Azure AD Plugin to version 1.2 or later where credentials are properly encrypted; rotate any credentials that may have been exposed.

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
Azure AdApplication
Affected:<= 1.1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Azure AD plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin directory (typically $JENKINS_HOME/plugins/azure-ad/ or check manifest files)
    Affected if Azure AD plugin is not present in the plugin list
  2. Determine the installed plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed tab > search for Azure AD - the version is shown in the table. Alternatively, inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin archive
    Affected if Version is 1.1.2 or earlier
  3. Verify if Azure AD credentials are configured
    Navigate to Manage Jenkins > Configure Global Security or check the plugin's configuration page (路径 varies by plugin version but typically under Configure System), look for Azure AD client ID and client secret fields that have values populated
    Affected if Azure AD client ID and/or client secret fields contain configured values

Environment is affected if Jenkins Azure AD Plugin version 1.1.2 or earlier is installed AND Azure AD credentials are configured in the Jenkins configuration.

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

Update Jenkins Azure AD Plugin to version 1.2 or later where credentials are properly encrypted; rotate any credentials that may have been exposed.

Fix this in Azure Ad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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