dbcve.org
Openid Connect AuthenticationApplication · Jenkins

CVE-2024-47807

HIGH · 8.1 CVSS v3.1 Published 2024-10-02
Fix available
A fix is available. Upgrade to 4.355.v3a_fb_fca_b_96d4 or later.
See remediation →
90/100
Remediation priority · Urgent
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 OpenId Connect Authentication Plugin 4.354.v321ce67a_1de8 and earlier does not check the `iss` (Issuer) claim of an ID Token, allowing attackers to subvert the authentication flow, potentially gaining administrator access to 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

The Jenkins OpenID Connect Authentication Plugin versions 4.354 and earlier fails to validate the `iss` (Issuer) claim in ID Tokens. This is a critical security check in OpenID Connect that verifies the token was issued by the expected identity provider. Without this validation, an attacker could potentially present a token from a malicious or unauthorized issuer to authenticate as a legitimate user and gain administrator access.

MitigationUpgrade the OpenID Connect Authentication Plugin to version 4.355 or later which implements proper `iss` claim validation. Before upgrading, backup the Jenkins configuration and test the update in a non-production environment to ensure authentication continues to work correctly.

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
Openid Connect AuthenticationApplication
Affected:< 4.355.v3a_fb_fca_b_96d4

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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 OpenID Connect Authentication Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'OpenID Connect' or 'openidconnect', or check the $JENKINS_HOME/plugins directory for the openid-connect* plugin folder
    Affected if The plugin is not installed (not vulnerable because functionality is not present)
  2. Determine installed plugin version
    In Manage Jenkins > Manage Plugins > Installed, locate the 'OpenID Connect Authentication' plugin and note the version number displayed
    Affected if Version is 4.354 or earlier (versions before 4.355 are affected)
  3. Check if OpenID Connect authentication is enabled
    Navigate to Manage Jenkins > Configure Global Security > Security Realm and verify 'OpenID Connect' is selected as the security realm
    Affected if OpenID Connect is not selected as the security realm (not vulnerable because the flawed authentication flow is not active)
  4. Verify OpenID Provider configuration
    Go to Manage Jenkins > Configure Global Security > OpenID Connect and check if an Issuer URL is configured under the OpenID Provider settings
    Affected if An Issuer URL is configured (the missing iss validation would apply to tokens from this issuer)

The environment is affected if the OpenID Connect Authentication Plugin versions 4.354 or earlier is installed AND OpenID Connect is configured as the active security realm with an issuer configured.

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 4.355.v3a_fb_fca_b_96d4 or later
Fixed in 4.355.v3a_fb_fca_b_96d4
Interim mitigation

Upgrade the OpenID Connect Authentication Plugin to version 4.355 or later which implements proper `iss` claim validation. Before upgrading, backup the Jenkins configuration and test the update in a non-production environment to ensure authentication continues to work correctly.

Recommended fix High confidence

OpenId Connect Authentication Plugin version 4.355.v3a_fb_fca_b_96d4 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the Updates tab
  3. 3. Locate 'OpenId Connect Authentication Plugin' in the available updates
  4. 4. Select the plugin and click 'Download now and install after restart' or 'Install'
  5. 5. Wait for the plugin to download and install
  6. 6. If prompted, restart Jenkins
  7. 7. After installation, verify the plugin version is 4.355.v3a_fb_fca_b_96d4 or later by going to Manage Jenkins > Manage Plugins > Installed tab
  8. 8. Confirm the authentication flow is working correctly with the OpenId Connect provider

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

Fix this in Openid Connect Authentication Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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