dbcve.org
Openid Connect AuthenticationApplication · Jenkins

CVE-2024-47806

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 `aud` (Audience) 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 fails to validate the `aud` (Audience) claim in ID Tokens. This claim verifies that a token was issued for the specific relying party (Jenkins). Without this check, attackers can use tokens intended for other applications to authenticate to Jenkins, potentially gaining administrator access.

MitigationUpgrade Jenkins OpenID Connect Authentication Plugin to version 4.355.v321ce67a_1de9 or later, which implements proper audience claim validation.

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 > Plugins > Installed and look for 'OpenID Connect Authentication' in the list of installed plugins, or use the Jenkins CLI: jenkins-cli.jar who-am-i or check $JENKINS_HOME/plugins for the openid-plugin directory.
    Affected if The plugin is not installed, the environment is not affected by this vulnerability.
  2. Check the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Plugins > Installed, find OpenID Connect Authentication, and note the version number. Compare this to the vulnerable version range: versions before 4.355.v3a_fb_fca_b_96d4 are affected.
    Affected if The installed version is lower than 4.355.v3a_fb_fca_b_96d4, the environment is vulnerable.
  3. Confirm OIDC authentication is configured as the Security Realm
    Go to Manage Jenkins > Security > Security Realm and verify if 'OpenID Connect Authentication' or 'OAuth' is selected as the current security realm. The vulnerability only applies when OIDC/OAuth is actively used for authentication.
    Affected if OIDC/OAuth authentication is not enabled as the Security Realm, the vulnerability is not exploitable in the current configuration.

A user is affected if the OpenID Connect Authentication Plugin version is below 4.355.v3a_fb_fca_b_96d4 AND OIDC authentication is configured as the Security Realm.

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 Jenkins OpenID Connect Authentication Plugin to version 4.355.v321ce67a_1de9 or later, which implements proper audience claim validation.

Recommended fix High confidence

OpenId Connect Authentication Plugin version 4.355.v3a_fb_fca_b_96d4 or later

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Installed' tab
  4. Find the 'OpenId Connect Authentication' plugin in the list
  5. Check if the current version is less than 4.355.v3a_fb_fca_b_96d4
  6. If vulnerable, click 'Update' to upgrade to the latest available version
  7. Restart Jenkins if required to complete the installation
  8. Verify the plugin version after update shows 4.355.v3a_fb_fca_b_96d4 or later

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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