Azure CredentialsApplication · Jenkins

CVE-2023-25768

MEDIUM · 6.5 CVSS v3.1 Published 2023-02-15

Fix available

A fix is available. Upgrade to 254.v64da_8176c83a or later.

See remediation →

71/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

A missing permission check in Jenkins Azure Credentials Plugin 253.v887e0f9e898b and earlier allows attackers with Overall/Read permission to connect to an attacker-specified web server.

Technical summary

dbcve analysis · high confidence

A missing permission check in Jenkins Azure Credentials Plugin versions 253.v887e0f9e898b and earlier allows attackers with Overall/Read permission to cause the Jenkins server to connect to attacker-specified web servers. This SSRF-like vulnerability enables attackers to make the Jenkins instance initiate connections to external systems without proper authorization.

MitigationUpgrade Jenkins Azure Credentials Plugin to version 254.v2b_cd25c54369 or later, which implements proper permission checks before allowing 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

NVD · CPE data

Azure CredentialsApplication

Affected:< 254.v64da_8176c83a

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Azure Credentials Plugin is installed

Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i azure-credentials

Affected if The Azure Credentials Plugin appears in the list of installed plugins
Determine the installed version of Azure Credentials Plugin

In the Manage Plugins > Installed tab, find Azure Credentials and note the Version column; alternatively, check the plugin's .jpi file in $JENKINS_HOME/plugins/ for the manifest version

Affected if The version is 253.v887e0f9e898b or earlier, or any version below 254.v64da_8176c83a
Verify Overall/Read permission is enabled

Navigate to Manage Jenkins > Manage Users > check if any users exist with Overall/Read access, or inspect $JENKINS_HOME/config.xml for <permission>settings</permission>

Affected if Overall/Read permission is granted to any user or anonymous access (which is the default configuration)
Check if Azure credential configurations are accessible

Navigate to Manage Credentials > System > Azure or inspect credential XML files in $JENKINS_HOME/credentials.xml for Azure-related entries

Affected if Azure credential definitions exist that could be leveraged to trigger HTTP connections

If the Azure Credentials Plugin version is below 254.v64da_8176c83a and Overall/Read permission is enabled, the environment is vulnerable to this SSRF-like flaw.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 254.v64da_8176c83a or later

Fixed in 254.v64da_8176c83a

Interim mitigation

Upgrade Jenkins Azure Credentials Plugin to version 254.v2b_cd25c54369 or later, which implements proper permission checks before allowing web server connections.

Recommended fix High confidence

254.v64da_8176c83a

Log in to Jenkins with administrator credentials
Navigate to 'Manage Jenkins'
Click on 'Manage Plugins'
Go to the 'Installed' tab
Locate 'Azure Credentials' plugin in the list
If an update is available, click 'Update' or install version 254.v64da_8176c83a
After update completes, restart Jenkins if prompted
Verify the plugin shows version 254.v64da_8176c83a or later

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
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

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,696.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.jenkins.ioVendor Advisory
www.openwall.comMailing ListThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25768 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-25768?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 254.v64da_8176c83a or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Azure Credentials

Remediation

Need this fixed?

Fix this in Azure Credentials 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2023-25768 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References