{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3868 in the wild and no public exploit code.","fix":"Upgrade org.keycloak:keycloak-core to 6.0.0 or later.","what":"CVE-2019-3868 is a low-severity vulnerability in Redhat Keycloak, published on 24 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-3868 and fix it if it is affected.\n\nWhat it is: CVE-2019-3868 is a low-severity vulnerability in Redhat Keycloak, published on 24 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-3868 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 6.0.0\n- org.keycloak:keycloak-core (Maven): affected all versions; fixed in 6.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-3868/ (Markdown: https://insights.sbomify.com/CVE-2019-3868/index.md)","id":"CVE-2019-3868","markdown":"https://insights.sbomify.com/CVE-2019-3868/index.md","name":"CVE-2019-3868","record":{"aliases":["GHSA-gc52-xj6p-9pxp","RHSA-2019:0856","RHSA-2019:0857"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"high_privilege","summary":"Attackers with backend access can hijack user browser sessions by using JWT tokens as session cookies in Keycloak.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"keycloak","vendor":"redhat"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user’s browser session.","ecosystems":["Maven","Red Hat:red_hat_single_sign_on:7::el6","Red Hat:red_hat_single_sign_on:7::el7"],"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":"Exposure of Sensitive Information to an Unauthorized Actor in Keycloak","id":"CVE-2019-3868","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:keycloak","products":["redhat:keycloak"],"type":"information_disclosure","year":"2019"},"n_packages":6,"n_references":4,"next":{"headline":"Information disclosure in Tower","id":"CVE-2019-3869"},"packages":[{"ecosystem":"Maven","fixed":["6.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":null,"source":"GHSA-gc52-xj6p-9pxp"},{"ecosystem":"Maven","fixed":["6.0.0"],"introduced":["0"],"last_affected":[],"package":"org.keycloak:keycloak-core","purl":"pkg:maven/org.keycloak/keycloak-core","source":"GHSA-gc52-xj6p-9pxp"},{"ecosystem":"Red Hat:red_hat_single_sign_on:7::el6","fixed":["0:3.4.17-1.Final_redhat_00001.1.jbcs.el6"],"introduced":["0"],"last_affected":[],"package":"rh-sso7-keycloak","purl":"pkg:rpm/redhat/rh-sso7-keycloak","source":"RHSA-2019:0857"},{"ecosystem":"Red Hat:red_hat_single_sign_on:7::el6","fixed":["0:3.4.17-1.Final_redhat_00001.1.jbcs.el6"],"introduced":["0"],"last_affected":[],"package":"rh-sso7-keycloak-server","purl":"pkg:rpm/redhat/rh-sso7-keycloak-server","source":"RHSA-2019:0857"},{"ecosystem":"Red Hat:red_hat_single_sign_on:7::el7","fixed":["0:3.4.17-1.Final_redhat_00001.1.jbcs.el7"],"introduced":["0"],"last_affected":[],"package":"rh-sso7-keycloak","purl":"pkg:rpm/redhat/rh-sso7-keycloak","source":"RHSA-2019:0856"},{"ecosystem":"Red Hat:red_hat_single_sign_on:7::el7","fixed":["0:3.4.17-1.Final_redhat_00001.1.jbcs.el7"],"introduced":["0"],"last_affected":[],"package":"rh-sso7-keycloak-server","purl":"pkg:rpm/redhat/rh-sso7-keycloak-server","source":"RHSA-2019:0856"}],"prev":{"headline":"Missing authorization in quay","id":"CVE-2019-3867"},"products":["keycloak"],"published":"2019-04-24","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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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 with backend access can hijack user browser sessions by using JWT tokens as session cookies in Keycloak.","url":"https://insights.sbomify.com/CVE-2019-3868/"}