{"answers":{"affected":"2 open source packages ship an affected version, including react-adal. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7787 in the wild and no public exploit code.","fix":"Upgrade react-adal to 0.5.1 or later.","what":"CVE-2020-7787 is a high-severity authentication bypass vulnerability in react-adal, published on 9 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7787 and fix it if it is affected.\n\nWhat it is: CVE-2020-7787 is a high-severity authentication bypass vulnerability in react-adal, published on 9 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7787 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- react-adal (npm): affected all versions; fixed in 0.5.1\n- react-adal (npm): affected all versions; fixed in 0.5.1\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-7787/ (Markdown: https://insights.sbomify.com/CVE-2020-7787/index.md)","id":"CVE-2020-7787","markdown":"https://insights.sbomify.com/CVE-2020-7787/index.md","name":"CVE-2020-7787","record":{"aliases":["GHSA-7mpx-vg3c-cmr4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"React ADAL library","requires_auth":"none","summary":"Attackers can bypass authentication in react-adal by exploiting storage logic to validate crafted JWT tokens as authentic.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"react-adal","vendor":"react-adal_project"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N/E:P/RL:T/RC:R","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"This affects all versions of package react-adal. It is possible for a specially crafted JWT token and request URL can cause the nonce, session and refresh values to be incorrectly validated, causing the application to treat an attacker-generated JWT token as authentic. The logical defect is caused by how the nonce, session and refresh values are stored in the browser local storage or session storage. Each key is automatically appended by ||. When the received nonce and session keys are generated, the list of values is stored in the browser storage, separated by ||, with || always appended to the end of the list. Since || will always be the last 2 characters of the stored values, an empty string (\"\") will always be in the list of the valid values. Therefore, if an empty session parameter is provided in the callback URL, and a specially-crafted JWT token contains an nonce value of \"\" (empty string), then adal.js will consider the JWT token as authentic.","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":"Improper Authentication","id":"CVE-2020-7787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Prototype Pollution","id":"CVE-2020-7788"},"packages":[{"ecosystem":"npm","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"react-adal","purl":null,"source":"GHSA-7mpx-vg3c-cmr4"},{"ecosystem":"npm","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"react-adal","purl":"pkg:npm/react-adal","source":"GHSA-7mpx-vg3c-cmr4"}],"prev":{"headline":"Command Injection","id":"CVE-2020-7786"},"products":["react-adal"],"published":"2020-12-09","related":[],"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":["n/a"]},"summary":"Attackers can bypass authentication in react-adal by exploiting storage logic to validate crafted JWT tokens as authentic.","url":"https://insights.sbomify.com/CVE-2020-7787/"}