Session fixation vulnerability in Jenkins OpenId Connect Authentication PluginGHSA-h23j-73ww-7594
HIGHGHSA-h23j-73ww-7594 is a high-severity (CVSS 8.8) CWE-613 vulnerability in org.jenkins-ci.plugins:oic-auth. A fix is available for org.jenkins-ci.plugins:oic-auth — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h23j-73ww-7594.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:oic-authReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins OpenId Connect Authentication Plugin 4.418.vccc7061f5b_6d and earlier does not invalidate the previous session on login. This allows attackers to use social engineering techniques to gain administrator access to Jenkins. OpenId Connect Authentication Plugin 4.421.v5422614eb_e0a_ invalidates the existing session on login.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:oic-auth | all versions | 4.421.v5422614eborg.jenkins-ci.plugins:oic-auth:4.421.v5422614eb |
Affected Products
openid connect authenticationjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:oic-auth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:oic-auth to 4.421.v5422614eb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h23j-73ww-7594 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-h23j-73ww-7594 in your dependencies?
Find it across Maven, including transitive dependencies.