{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-35207 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35207 is a medium-severity authentication bypass vulnerability in n/a, published on 12 Dec 2020. 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-2020-35207 and fix it if it is affected.\n\nWhat it is: CVE-2020-35207 is a medium-severity authentication bypass vulnerability in n/a, published on 12 Dec 2020. 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-2020-35207 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-2020-35207/ (Markdown: https://insights.sbomify.com/CVE-2020-35207/index.md)","id":"CVE-2020-35207","markdown":"https://insights.sbomify.com/CVE-2020-35207/index.md","name":"CVE-2020-35207","record":{"aliases":["GHSA-2qrc-66qm-fhmc"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"LastPass iOS app","requires_auth":"none","summary":"Attackers on jailbroken devices can bypass PIN authentication in the LastPass iOS app via runtime manipulation, though the vendor deems this out of scope.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lastpass","vendor":"logmein"}],"cvss":{"score":5.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An issue was discovered in the LogMein LastPass Password Manager (aka com.lastpass.ilastpass) app 4.8.11.2403 for iOS. The PIN authentication for unlocking can be bypassed by forcing the authentication result to be true through runtime manipulation. In other words, an attacker could authenticate with an arbitrary PIN. NOTE: the vendor has indicated that this is not an attack of interest within the context of their threat model, which excludes jailbroken devices","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":"Auth bypass in n/a","id":"CVE-2020-35207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2020-35208"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-35206"},"products":["n/a"],"published":"2020-12-12","related":[{"cvss_score":8.2,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-16371","kev_date_added":null,"published":"2019-09-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2018-10193","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":6.8,"headline":"Weak cryptography in n/a","id":"CVE-2013-5113","kev_date_added":null,"published":"2020-01-31"},{"cvss_score":6.1,"headline":"Security feature bypass in n/a","id":"CVE-2013-5114","kev_date_added":null,"published":"2020-01-31"},{"cvss_score":5.7,"headline":"Auth bypass in n/a","id":"CVE-2020-35208","kev_date_added":null,"published":"2020-12-12"}],"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":["n/a"]},"summary":"Attackers on jailbroken devices can bypass PIN authentication in the LastPass iOS app via runtime manipulation, though the vendor deems this out of scope.","url":"https://insights.sbomify.com/CVE-2020-35207/"}