# 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.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-g58x-57fv-86jh

## 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 (Incorrect Comparison)

## 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 | Ecosystem | 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: 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](https://insights.sbomify.com/CVE-2015-5298/): Jenkins Google Login Plugin 1.0 and 1.1 allows anonymous users to authenticate through client-side request modification (medium 6.5)
- [CVE-2022-46683](https://insights.sbomify.com/CVE-2022-46683/): Jenkins Google Login Plugin Open Redirect vulnerability (medium 6.1)
- [CVE-2018-1000174](https://insights.sbomify.com/CVE-2018-1000174/): Jenkins Google Login Plugin Open Redirect vulnerability (medium 6.1)
- [CVE-2018-1000173](https://insights.sbomify.com/CVE-2018-1000173/): Jenkins Google Login Plugin Session Fixation vulnerability (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41936 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2023-41936 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:google-login (Maven): affected all versions; fixed in 1.8
- org.jenkins-ci.plugins:google-login (Maven): affected all versions; fixed in 1.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-41936/ (Markdown: https://insights.sbomify.com/CVE-2023-41936/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-41936
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-41936
- OSV: https://osv.dev/vulnerability/CVE-2023-41936

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-41936/
Summaries are generated and may contain mistakes; the official description above is the record.