{"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-2015-5298 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:google-login to 1.2 or later.","what":"CVE-2015-5298 is a medium-severity authentication bypass vulnerability in Jenkins Google Login Plugin, published on 7 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-5298 and fix it if it is affected.\n\nWhat it is: CVE-2015-5298 is a medium-severity authentication bypass vulnerability in Jenkins Google Login Plugin, published on 7 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-5298 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:google-login (Maven): affected from 1.0; fixed in 1.2\n- org.jenkins-ci.plugins:google-login (Maven): affected from 1.0; fixed in 1.2\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-2015-5298/ (Markdown: https://insights.sbomify.com/CVE-2015-5298/index.md)","id":"CVE-2015-5298","markdown":"https://insights.sbomify.com/CVE-2015-5298/index.md","name":"CVE-2015-5298","record":{"aliases":["GHSA-p487-39h9-hm84"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Jenkins Google Login Plugin","requires_auth":"low_privilege","summary":"Attackers can bypass domain restrictions in the Jenkins Google Login Plugin to authenticate against locked-down instances via client-side request modification.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"google_login","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"The Google Login Plugin (versions 1.0 and 1.1) allows malicious anonymous users to authenticate successfully against Jenkins instances that are supposed to be locked down to a particular Google Apps domain through client-side request modification.","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 1.0 and 1.1 allows anonymous users to authenticate through client-side request modification","id":"CVE-2015-5298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2015"},"n_packages":2,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2015-5299"},"packages":[{"ecosystem":"Maven","fixed":["1.2"],"introduced":["1.0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-login","purl":null,"source":"GHSA-p487-39h9-hm84"},{"ecosystem":"Maven","fixed":["1.2"],"introduced":["1.0"],"last_affected":[],"package":"org.jenkins-ci.plugins:google-login","purl":"pkg:maven/org.jenkins-ci.plugins/google-login","source":"GHSA-p487-39h9-hm84"}],"prev":{"headline":"Integer overflow in pixman","id":"CVE-2015-5297"},"products":["Jenkins Google Login Plugin"],"published":"2022-07-07","related":[{"cvss_score":7.5,"headline":"Jenkins Google Login Plugin non-constant time token comparison","id":"CVE-2023-41936","kev_date_added":null,"published":"2023-09-06"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Attackers can bypass domain restrictions in the Jenkins Google Login Plugin to authenticate against locked-down instances via client-side request modification.","url":"https://insights.sbomify.com/CVE-2015-5298/"}