{"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-2020-1725 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-parent to 13.0.0 or later.","what":"CVE-2020-1725 is a medium-severity missing authorization vulnerability in Redhat Keycloak, published on 28 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1725 and fix it if it is affected.\n\nWhat it is: CVE-2020-1725 is a medium-severity missing authorization vulnerability in Redhat Keycloak, published on 28 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-1725 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 13.0.0\n- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 13.0.0\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-2020-1725/ (Markdown: https://insights.sbomify.com/CVE-2020-1725/index.md)","id":"CVE-2020-1725","markdown":"https://insights.sbomify.com/CVE-2020-1725/index.md","name":"CVE-2020-1725","record":{"aliases":["GHSA-p225-pc2x-4jpm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity provider","requires_auth":"low_privilege","summary":"Users retain access to resources after role changes due to stale access tokens, allowing unauthorized access in Keycloak.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A flaw was found in keycloak before version 13.0.0. In some scenarios a user still has access to a resource after changing the role mappings in Keycloak and after expiration of the previous access 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":"Incorrect Authorization in keycloak","id":"CVE-2020-1725","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak"],"type":"missing_authorization","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Podman has Files or Directories Accessible to External Parties","id":"CVE-2020-1726"},"packages":[{"ecosystem":"Maven","fixed":["13.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-parent","purl":null,"source":"GHSA-p225-pc2x-4jpm"},{"ecosystem":"Maven","fixed":["13.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-parent","purl":"pkg:maven/org.keycloak/keycloak-parent","source":"GHSA-p225-pc2x-4jpm"}],"prev":{"headline":"Keycloak Insufficient Session Expiry","id":"CVE-2020-1724"},"products":["keycloak"],"published":"2021-01-28","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-08-04","vendors":["n/a"]},"summary":"Users retain access to resources after role changes due to stale access tokens, allowing unauthorized access in Keycloak.","url":"https://insights.sbomify.com/CVE-2020-1725/"}