{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-36689 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-36689 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-36689 is a medium-severity vulnerability in n/a, published on 3 Mar 2023. 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-2021-36689 and fix it if it is affected.\n\nWhat it is: CVE-2021-36689 is a medium-severity vulnerability in n/a, published on 3 Mar 2023. 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-2021-36689 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2021-36689/ (Markdown: https://insights.sbomify.com/CVE-2021-36689/index.md)","id":"CVE-2021-36689","markdown":"https://insights.sbomify.com/CVE-2021-36689/index.md","name":"CVE-2021-36689","record":{"aliases":["GHSA-j77q-57r3-74g7"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samourai Wallet","requires_auth":"low_privilege","summary":"Attackers can decrypt sensitive wallet data by brute-forcing the short PIN if they possess the recovered data file.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"samourai-wallet-android","vendor":"samourai-wallet-android_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"An issue discovered in com.samourai.wallet.PinEntryActivity.java in Streetside Samourai Wallet 0.99.96i allows attackers to view sensitive information and decrypt data via a brute force attack that uses a recovered samourai.dat file. The PIN is 5 to 8 digits, which may be insufficient in this situation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2021-36689","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2021-36690"},"packages":[],"prev":{"headline":"Cross-site Scripting in yapi-vendor","id":"CVE-2021-36686"},"products":["n/a"],"published":"2023-03-03","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-07","vendors":["n/a"]},"summary":"Attackers can decrypt sensitive wallet data by brute-forcing the short PIN if they possess the recovered data file.","url":"https://insights.sbomify.com/CVE-2021-36689/"}