CVE-2023-41936
First published: Wed Sep 06 2023(Updated: )
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.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Google Login | <=1.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2023-41936?
CVE-2023-41936 is a vulnerability in the Jenkins Google Login Plugin that allows attackers to obtain a valid token using statistical methods.
What is the severity of CVE-2023-41936?
The severity of CVE-2023-41936 is high with a CVSS score of 7.5.
How does CVE-2023-41936 affect Jenkins Google Login Plugin?
CVE-2023-41936 affects Jenkins Google Login Plugin versions 1.7 and earlier.
How can attackers exploit CVE-2023-41936?
Attackers can exploit CVE-2023-41936 by using statistical methods to obtain a valid token.
Are there any patches or fixes available for CVE-2023-41936?
Yes, the Jenkins security advisory provides details on how to fix CVE-2023-41936.
- collector/nvd-api
- collector/nvd-index
- agent/event
- agent/references
- agent/author
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/weakness
- agent/severity
- agent/description
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- vendor/jenkins
- canonical/jenkins google login
- version/jenkins google login/1.7