{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-12160 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-parent to 3.3.0.Final or later.","what":"CVE-2017-12160 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 26 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-12160 and fix it if it is affected.\n\nWhat it is: CVE-2017-12160 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 26 Oct 2017. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-12160 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 3.3.0.Final\n- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 3.3.0.Final\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-2017-12160/ (Markdown: https://insights.sbomify.com/CVE-2017-12160/index.md)","id":"CVE-2017-12160","markdown":"https://insights.sbomify.com/CVE-2017-12160/index.md","name":"CVE-2017-12160","record":{"aliases":["GHSA-qc72-gfvw-76h7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"high_privilege","summary":"An attacker with a compromised resource can retain indefinite access tokens despite permission revocation, bypassing authorization controls in Keycloak.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.","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":"Keycloak Oauth Implementation Error","id":"CVE-2017-12160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak"],"type":"auth_bypass","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Moderate severity vulnerability that affects org.keycloak:keycloak-core","id":"CVE-2017-12161"},"packages":[{"ecosystem":"Maven","fixed":["3.3.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-parent","purl":null,"source":"GHSA-qc72-gfvw-76h7"},{"ecosystem":"Maven","fixed":["3.3.0.Final"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-parent","purl":"pkg:maven/org.keycloak/keycloak-parent","source":"GHSA-qc72-gfvw-76h7"}],"prev":{"headline":"Keycloak CSRF Vulnerability","id":"CVE-2017-12159"},"products":["keycloak"],"published":"2017-10-26","related":[{"cvss_score":10,"headline":"Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC","id":"CVE-2022-4361","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":9.8,"headline":"Keycloak vulnerable to privilege escalation on Token Exchange feature","id":"CVE-2022-1245","kev_date_added":null,"published":"2022-07-07"},{"cvss_score":9.6,"headline":"keycloak Self Stored Cross-site Scripting vulnerability","id":"CVE-2021-20195","kev_date_added":null,"published":"2021-05-28"},{"cvss_score":9.3,"headline":"Keycloak Authentication Error","id":"CVE-2019-14910","kev_date_added":null,"published":"2019-12-05"},{"cvss_score":9.3,"headline":"Keycloak Authentication Error","id":"CVE-2019-14909","kev_date_added":null,"published":"2019-12-04"},{"cvss_score":9.1,"headline":"Keycloak vulnerable to path traversal via double URL encoding","id":"CVE-2022-3782","kev_date_added":null,"published":"2023-01-11"},{"cvss_score":9.1,"headline":"keycloak vulnerable to unauthorized login via mail server setup","id":"CVE-2019-14837","kev_date_added":null,"published":"2020-01-07"}],"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-09-16","vendors":["Red Hat, Inc."]},"summary":"An attacker with a compromised resource can retain indefinite access tokens despite permission revocation, bypassing authorization controls in Keycloak.","url":"https://insights.sbomify.com/CVE-2017-12160/"}