CVE-2023-41936 Jenkins Google Login Plugin non-constant time token comparison
Attackers can bypass authentication in the Jenkins Google Login Plugin by exploiting a timing side-channel to obtain valid tokens.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-41936?
CVE-2023-41936 is a high-severity vulnerability in Jenkins Google Login Plugin, published on 6 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Jenkins Google Login Plugin 1.7 and earlier uses a non-constant time comparison function when checking whether the provided and expected token are equal, potentially allowing attackers to use statistical methods to obtain a valid token.
Weakness: CWE-697
Which versions are affected by CVE-2023-41936?
2 open source packages ship an affected version, including org.jenkins-ci.plugins:google-login. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.jenkins-ci.plugins:google-login Maven | All versions | 1.8 |
org.jenkins-ci.plugins:google-login Maven | All versions | 1.8 |
Products include Jenkins Google Login.
How do I fix CVE-2023-41936?
Upgrade org.jenkins-ci.plugins:google-login to 1.8 or later.
Is CVE-2023-41936 being exploited?
There is no known exploitation of CVE-2023-41936 in the wild and no public exploit code.
Other vulnerabilities in Jenkins Google Login Plugin
- CVE-2015-5298 Jenkins Google Login Plugin 1.0 and 1.1 allows anonymous users to authenticate through client-side request modification
- CVE-2022-46683 Jenkins Google Login Plugin Open Redirect vulnerability
- CVE-2018-1000174 Jenkins Google Login Plugin Open Redirect vulnerability
- CVE-2018-1000173 Jenkins Google Login Plugin Session Fixation vulnerability
Sources
Also known as GHSA-g58x-57fv-86jh.