{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-3891 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-3891 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-3891 is a low-severity vulnerability in Apple Ipad Os, published on 1 Apr 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-3891 and fix it if it is affected.\n\nWhat it is: CVE-2020-3891 is a low-severity vulnerability in Apple Ipad Os, published on 1 Apr 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-3891 in the wild and no public exploit code.\n\nAffected product: Apple Ipad Os. 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-3891/ (Markdown: https://insights.sbomify.com/CVE-2020-3891/index.md)","id":"CVE-2020-3891","markdown":"https://insights.sbomify.com/CVE-2020-3891/index.md","name":"CVE-2020-3891","record":{"aliases":["GHSA-c887-fjhv-3qfj"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"iOS and watchOS","requires_auth":"none","summary":"Attackers with physical access can bypass reply restrictions on locked devices to respond to messages.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apple","cpe":[{"product":"ipad_os","vendor":"apple"},{"product":"iphone_os","vendor":"apple"},{"product":"watchos","vendor":"apple"}],"cvss":{"score":2.4,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[],"description":"A logic issue was addressed with improved state management. This issue is fixed in iOS 13.4 and iPadOS 13.4, watchOS 6.2. A person with physical access to a locked iOS device may be able to respond to messages even when replies are disabled.","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":"Security feature bypass in iOS","id":"CVE-2020-3891","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apple:ipad_os","products":["apple:ipad_os","apple:iphone_os","apple:watchos"],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in macOS","id":"CVE-2020-3892"},"packages":[],"prev":{"headline":"Information disclosure in iOS","id":"CVE-2020-3890"},"products":["iOS","watchOS"],"published":"2020-04-01","related":[{"cvss_score":9.8,"headline":"Memory corruption in iOS and iPadOS","id":"CVE-2021-1794","kev_date_added":null,"published":"2021-04-02"},{"cvss_score":9.8,"headline":"Memory corruption in iOS and iPadOS","id":"CVE-2021-1795","kev_date_added":null,"published":"2021-04-02"},{"cvss_score":9.8,"headline":"Memory corruption in iOS and iPadOS","id":"CVE-2021-1796","kev_date_added":null,"published":"2021-04-02"},{"cvss_score":9.8,"headline":"Memory corruption in iOS and iPadOS","id":"CVE-2021-1818","kev_date_added":null,"published":"2021-04-02"},{"cvss_score":9.1,"headline":"Auth bypass in iOS and iPadOS","id":"CVE-2024-23255","kev_date_added":null,"published":"2024-03-08"},{"cvss_score":8.8,"headline":"Memory corruption in iOS and iPadOS","id":"CVE-2024-23226","kev_date_added":null,"published":"2024-03-08"},{"cvss_score":8.8,"headline":"Memory corruption in Safari","id":"CVE-2022-22610","kev_date_added":null,"published":"2022-09-23"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Apple"]},"summary":"Attackers with physical access can bypass reply restrictions on locked devices to respond to messages.","url":"https://insights.sbomify.com/CVE-2020-3891/"}