dbcve.org
Azure CredentialsApplication · Jenkins

CVE-2023-25767

HIGH · 8.8 CVSS v3.1 Published 2023-02-15
Fix available
A fix is available. Upgrade to 254.v64da_8176c83a 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 (CSRF) vulnerability in Jenkins Azure Credentials Plugin 253.v887e0f9e898b and earlier allows attackers to connect to an attacker-specified web server.

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

This is a CSRF vulnerability in the Jenkins Azure Credentials Plugin that allows attackers to trick authenticated Jenkins users into triggering the server to connect to an attacker-controlled web server. The vulnerability exists because the plugin lacks proper CSRF token validation on sensitive endpoints.

MitigationUpgrade the Jenkins Azure Credentials Plugin to the latest version that includes CSRF protection (form token/crumb validation) on endpoints that initiate web server connections.

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 CredentialsApplication
Affected:< 254.v64da_8176c83a

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 installed Azure Credentials Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, then locate 'Azure Credentials' in the list to view the installed version number. Alternatively, query the Jenkins REST API at /pluginManager/plugin/azure-credentials or check the plugin manifest file in JENKINS_HOME/plugins/azure-credentials.jpi.
    Affected if The installed version is lower than 254.v64da_8176c83a (e.g., 253.x, 252.x, etc.)
  2. Confirm plugin is loaded and active
    Verify the Azure Credentials plugin shows as 'Enabled' in the plugin manager. A CSRF attack only affects users who have this plugin loaded in their active Jenkins instance.
    Affected if The plugin is installed and enabled in Jenkins.
  3. Check for Azure credential configurations
    Navigate to Manage Jenkins > Manage Credentials > System > Global credentials (or Azure-specific credential domains if configured). Look for any credential entries with type 'Azure' or 'Microsoft Azure Service Principal'.
    Affected if Any Azure credentials are configured in Jenkins - these are the credentials that could be triggered via the vulnerable CSRF-prone endpoints.
  4. Verify endpoint exposure (optional verification)
    Review Jenkins logs or network traffic for connections from Jenkins to unexpected external hosts, particularly after user authentication. The CSRF flaw allows an attacker to trigger Jenkins to connect to attacker-controlled servers using configured Azure credentials.
    Affected if Jenkins makes outbound connections to unfamiliar external IP addresses or domains after users authenticate.

You are affected if the Jenkins Azure Credentials Plugin version is below 254.v64da_8176c83a AND the plugin is enabled with Azure credentials configured in your Jenkins instance.

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 254.v64da_8176c83a or later
Fixed in 254.v64da_8176c83a
Interim mitigation

Upgrade the Jenkins Azure Credentials Plugin to the latest version that includes CSRF protection (form token/crumb validation) on endpoints that initiate web server connections.

Recommended fix High confidence

Azure Credentials Plugin version 254.v64da_8176c83a or later

  1. 1. In the Jenkins web interface, navigate to 'Manage Jenkins' and select 'Manage Plugins'.
  2. 2. Click on the 'Updates' tab to see available plugin updates.
  3. 3. Locate 'Azure Credentials' plugin in the list of updates.
  4. 4. Select the checkbox next to Azure Credentials plugin.
  5. 5. Click the 'Download now and install after restart' button, or click 'Install' to install immediately.
  6. 6. Wait for the plugin to download and install.
  7. 7. If prompted, restart Jenkins to complete the installation.
  8. 8. Verify the installed version is 254.v64da_8176c83a or later by checking 'Manage Plugins' > 'Installed' tab.

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

Fix this in Azure Credentials Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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