dbcve.org
Azure AdApplication · Jenkins

CVE-2021-21679

HIGH · 8.8 CVSS v3.1 Published 2021-08-31
Fix available
A fix is available. Upgrade to after 179.vf6841393099e 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
Jenkins Azure AD Plugin 179.vf6841393099e and earlier allows attackers to craft URLs that would bypass the CSRF protection of any target URL 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

Jenkins Azure AD Plugin versions 179.vf6841393099e and earlier contains a CSRF protection bypass vulnerability. Attackers can craft malicious URLs that circumvent Jenkins' built-in CSRF token (crumb) validation for any target URL, potentially allowing unauthorized state-changing actions to be performed on behalf of authenticated users.

MitigationUpgrade the Jenkins Azure AD Plugin to version 180 or later to remediate the CSRF bypass vulnerability.

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:>= 164.v5b48baa961d2, <= 179.vf6841393099e

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. Verify the Azure AD Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Azure AD', or inspect the plugins directory (typically $JENKINS_HOME/plugins/) for the azure-ad.jpi or azure-ad.hpi file.
    Affected if The Azure AD plugin file exists in the Jenkins plugins directory.
  2. Determine the installed plugin version
    If using the web UI, view the plugin details page to read the Version field. If inspecting the file directly, open the MANIFEST.MF file inside the azure-ad.jpi/.hpi archive and locate the 'Implementation-Version' or 'Plugin-Version' attribute.
    Affected if The plugin is installed and you can read its version number.
  3. Compare the version against the affected range
    Check if your installed version falls between 164.v5b48baa961d2 and 179.vf6841393099e inclusive. Versions at or below 179.vf6841393099e are vulnerable; versions 180 and above are not.
    Affected if The installed version is 179.vf6841393099e or earlier, or the version starts with 164. or any number between 164 and 179.
  4. Confirm the plugin is configured and active
    Navigate to Manage Jenkins > Configure Global Security > Security Realm, or check Manage Jenkins > Configure System for Azure AD configuration section. Verify whether Azure AD authentication is actively configured (look for Client ID, Client Secret, or Tenant ID fields populated).
    Affected if The Azure AD Plugin has Azure AD credentials (Client ID/Client Secret) configured in Jenkins global configuration, making the CSRF bypass exploitable in authentication workflows.

You are affected if the Azure AD Plugin is installed with a version between 164.v5b48baa961d2 and 179.vf6841393099e inclusive, and the plugin is configured with Azure AD credentials for authentication.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 179.vf6841393099e
Interim mitigation

Upgrade the Jenkins Azure AD Plugin to version 180 or later to remediate the CSRF bypass vulnerability.

Recommended fix Moderate confidence

Azure AD Plugin version newer than 179.vf6841393099e (check Jenkins plugin repository for latest stable release)

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the Installed tab
  3. 3. Search for 'Azure AD' plugin
  4. 4. If the currently installed version is 179.vf6841393099e or earlier, click 'Update' to upgrade to the latest available version
  5. 5. Restart Jenkins after the plugin update completes
  6. 6. Verify the plugin version has been updated to a version newer than 179.vf6841393099e

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Ad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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