{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:google-login. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41936 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:google-login to 1.8 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2023-41936 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2023-41936 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:google-login (Maven): affected all versions; fixed in 1.8\n- org.jenkins-ci.plugins:google-login (Maven): affected all versions; fixed in 1.8\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-41936/ (Markdown: https://insights.sbomify.com/CVE-2023-41936/index.md)","id":"CVE-2023-41936","markdown":"https://insights.sbomify.com/CVE-2023-41936/index.md","name":"CVE-2023-41936","record":{"aliases":["GHSA-g58x-57fv-86jh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Google Login Plugin","requires_auth":"none","summary":"Attackers can bypass authentication in the Jenkins Google Login Plugin by exploiting a timing side-channel to obtain valid tokens.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"google_login","vendor":"jenkins"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins Google Login Plugin non-constant time token comparison","id":"CVE-2023-41936","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"SSRF vulnerability in Jenkins Bitbucket Push and Pull Request Plugin allows capturing credentials","id":"CVE-2023-41937"},"packages":[{"ecosystem":"Maven","fixed":["1.8"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-login","purl":null,"source":"GHSA-g58x-57fv-86jh"},{"ecosystem":"Maven","fixed":["1.8"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-login","purl":"pkg:maven/org.jenkins-ci.plugins/google-login","source":"GHSA-g58x-57fv-86jh"}],"prev":{"headline":"Non-constant time nonce comparison in Jenkins Microsoft Entra ID (previously Azure AD) Plugin","id":"CVE-2023-41935"},"products":["Jenkins Google Login Plugin"],"published":"2023-09-06","related":[{"cvss_score":6.5,"headline":"Jenkins Google Login Plugin 1.0 and 1.1 allows anonymous users to authenticate through client-side request modification","id":"CVE-2015-5298","kev_date_added":null,"published":"2022-07-07"},{"cvss_score":6.1,"headline":"Jenkins Google Login Plugin Open Redirect vulnerability","id":"CVE-2022-46683","kev_date_added":null,"published":"2022-12-07"},{"cvss_score":6.1,"headline":"Jenkins Google Login Plugin Open Redirect vulnerability","id":"CVE-2018-1000174","kev_date_added":null,"published":"2018-05-08"},{"cvss_score":5.9,"headline":"Jenkins Google Login Plugin Session Fixation vulnerability","id":"CVE-2018-1000173","kev_date_added":null,"published":"2018-05-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["Jenkins Project"]},"summary":"Attackers can bypass authentication in the Jenkins Google Login Plugin by exploiting a timing side-channel to obtain valid tokens.","url":"https://insights.sbomify.com/CVE-2023-41936/"}