{"answers":{"affected":"2 open source packages ship an affected version, including keycloak-connect. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-10157 in the wild and no public exploit code.","fix":"Upgrade keycloak-connect to 4.8.3 or later.","what":"CVE-2019-10157 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 12 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10157 and fix it if it is affected.\n\nWhat it is: CVE-2019-10157 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 12 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10157 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keycloak-connect (npm): affected all versions; fixed in 4.8.3\n- keycloak-connect (npm): affected all versions; fixed in 4.8.3\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-10157/ (Markdown: https://insights.sbomify.com/CVE-2019-10157/index.md)","id":"CVE-2019-10157","markdown":"https://insights.sbomify.com/CVE-2019-10157/index.md","name":"CVE-2019-10157","record":{"aliases":["GHSA-68hw-vfh7-xvg8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Keycloak Node.js adapter","requires_auth":"low_privilege","summary":"An attacker with local access can craft a malicious token to prevent user access indefinitely due to improper token verification in the Keycloak Node.js adapter.","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":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received from the server in its backchannel logout . An attacker with local access could use this to construct a malicious web token setting an NBF parameter that could prevent user access indefinitely.","ecosystems":["npm"],"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":"Forced Logout in keycloak-connect","id":"CVE-2019-10157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"redhat:keycloak","products":["redhat:keycloak","redhat:single_sign-on"],"type":"auth_bypass","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Improper implementation of the session fixation protection in Infinispan","id":"CVE-2019-10158"},"packages":[{"ecosystem":"npm","fixed":["4.8.3"],"introduced":["0"],"last_affected":[],"package":"keycloak-connect","purl":null,"source":"GHSA-68hw-vfh7-xvg8"},{"ecosystem":"npm","fixed":["4.8.3"],"introduced":["0"],"last_affected":[],"package":"keycloak-connect","purl":"pkg:npm/keycloak-connect","source":"GHSA-68hw-vfh7-xvg8"}],"prev":{"headline":"Exposure of Sensitive Information to an Unauthorized Actor in ansible","id":"CVE-2019-10156"},"products":["keycloak"],"published":"2019-06-12","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":"An attacker with local access can craft a malicious token to prevent user access indefinitely due to improper token verification in the Keycloak Node.js adapter.","url":"https://insights.sbomify.com/CVE-2019-10157/"}