OpenidApplication · Jenkins
CVE-2023-50770
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 · uneditedJenkins OpenId Connect Authentication Plugin 2.6 and earlier stores a password of a local user account used as an anti-lockout feature in a recoverable format, allowing attackers with access to the Jenkins controller file system to recover the plain text password of that account, likely 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 confidenceThe Jenkins OpenId Connect Authentication Plugin 2.6 and earlier stores the password of a local user account (used as an anti-lockout feature) in a recoverable format on the Jenkins controller file system. Attackers with file system access can recover the plaintext password and potentially gain administrator access to Jenkins.
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
OpenidApplication
<= 2.6CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify OpenId Connect Authentication Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab. Locate 'OpenId Connect Authentication Plugin' (may be listed as 'Openid' or 'OpenId Connect') and check the Version column.Affected if The installed version is 2.6 or earlier (e.g., 2.6, 2.5, 2.4, etc.)
-
Confirm plugin is configured and activeGo to Manage Jenkins > Configure Global Security > Security Realm. Verify that 'OpenId Connect Authentication' is selected as the security realm.Affected if The plugin is actively used as the authentication method, meaning the anti-lockout local account exists and its password is stored.
-
Locate plugin configuration directoryOn the Jenkins controller, navigate to the Jenkins home directory (usually $JENKINS_HOME). Look for plugin-related configuration files in the war directory or within the specific plugin's configuration folder under $JENKINS_HOME/plugins/ or $JENKINS_HOME/userContent/.Affected if Configuration files related to the OpenId Connect plugin exist on the file system.
-
Inspect stored credentialsSearch within the plugin configuration files for strings related to 'password', 'secret', 'anti-lockout', or similar. Examine any XML, XML, or configuration files that may contain the stored password in Base64-encoded or otherwise recoverable format.Affected if A password field contains a value that is not in plain text but is recoverable (e.g., Base64 encoded, encrypted with a known key, or stored in a reversible format).
A defender is affected if the OpenId Connect Authentication Plugin version is 2.6 or earlier AND the plugin is configured as the security realm, as this means the anti-lockout account password is stored in a recoverable format on disk.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to Jenkins OpenId Connect Authentication Plugin version 2.7 or later, which addresses the insecure storage of the anti-lockout account password.
Fix this in Openid
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-50770 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50770 in production — separate from our analysis above.
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.
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.
- 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