{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-10201 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-core to 7.0.0 or later.","what":"CVE-2019-10201 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 14 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10201 and fix it if it is affected.\n\nWhat it is: CVE-2019-10201 is a high-severity authentication bypass vulnerability in Redhat Keycloak, published on 14 Aug 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10201 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 7.0.0\n- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 7.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-2019-10201/ (Markdown: https://insights.sbomify.com/CVE-2019-10201/index.md)","id":"CVE-2019-10201","markdown":"https://insights.sbomify.com/CVE-2019-10201/index.md","name":"CVE-2019-10201","record":{"aliases":["GHSA-4fgq-gq9g-3rw7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak SAML broker","requires_auth":"low_privilege","summary":"Attackers can bypass SAML signature verification to impersonate users and access sensitive information in Keycloak.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"},{"product":"single_sign-on","vendor":"redhat"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-592","name":"DEPRECATED: Authentication Bypass Issues"}],"description":"It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the \u003cSignature\u003e sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.","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":"Improper Verification of Cryptographic Signature in keycloak","id":"CVE-2019-10201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak","redhat:single_sign-on"],"type":"auth_bypass","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Deserialization of Untrusted Data in org.codehaus.jackson:jackson-mapper-asl","id":"CVE-2019-10202"},"packages":[{"ecosystem":"Maven","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":null,"source":"GHSA-4fgq-gq9g-3rw7"},{"ecosystem":"Maven","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":"pkg:maven/org.keycloak/keycloak-core","source":"GHSA-4fgq-gq9g-3rw7"}],"prev":{"headline":"Privilege escalation in OpenShift Container Platform","id":"CVE-2019-10200"},"products":["keycloak"],"published":"2019-08-14","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":["Red Hat"]},"summary":"Attackers can bypass SAML signature verification to impersonate users and access sensitive information in Keycloak.","url":"https://insights.sbomify.com/CVE-2019-10201/"}