{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26236 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26236 is a high-severity vulnerability in ScratchVerifier, published on 20 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26236 and fix it if it is affected.\n\nWhat it is: CVE-2020-26236 is a high-severity vulnerability in ScratchVerifier, published on 20 Nov 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26236 in the wild and no public exploit code.\n\nAffected product: ScratchVerifier. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-26236/ (Markdown: https://insights.sbomify.com/CVE-2020-26236/index.md)","id":"CVE-2020-26236","markdown":"https://insights.sbomify.com/CVE-2020-26236/index.md","name":"CVE-2020-26236","record":{"aliases":["GHSA-99cr-hvf7-85g9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"ScratchVerifier authentication","requires_auth":"none","summary":"An attacker can hijack the verification process to log into another user's account by racing to complete the login after the victim submits the code.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"scratchverifier","vendor":"scratchverifier"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"In ScratchVerifier before commit a603769, an attacker can hijack the verification process to log into someone else's account on any site that uses ScratchVerifier for logins. A possible exploitation would follow these steps: 1. User starts login process. 2. Attacker attempts login for user, and is given the same verification code. 3. User comments code as part of their normal login. 4. Before user can, attacker completes the login process now that the code is commented. 5. User gets a failed login and attacker now has control of the account. Since commit a603769 starting a login twice will generate different verification codes, causing both user and attacker login to fail. For clients that rely on a clone of ScratchVerifier not hosted by the developers, their users may attempt to finish the login process as soon as possible after commenting the code. There is no reliable way for the attacker to know before the user can finish the process that the user has commented the code, so this vulnerability only really affects those who comment the code and then take several seconds before finishing the login.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Verification Code Hijacking in ScratchVerifier","id":"CVE-2020-26236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Prototype Pollution in highlight.js","id":"CVE-2020-26237"},"packages":[],"prev":{"headline":"Segmentation fault in Rust time crate","id":"CVE-2020-26235"},"products":["ScratchVerifier"],"published":"2020-11-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["ScratchVerifier"]},"summary":"An attacker can hijack the verification process to log into another user's account by racing to complete the login after the victim submits the code.","url":"https://insights.sbomify.com/CVE-2020-26236/"}