{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-8699 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-8699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-8699 is a high-severity vulnerability in Apple Iphone Os, published on 18 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-8699 and fix it if it is affected.\n\nWhat it is: CVE-2019-8699 is a high-severity vulnerability in Apple Iphone Os, published on 18 Dec 2019. 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-2019-8699 in the wild and no public exploit code.\n\nAffected product: Apple Iphone 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-2019-8699/ (Markdown: https://insights.sbomify.com/CVE-2019-8699/index.md)","id":"CVE-2019-8699","markdown":"https://insights.sbomify.com/CVE-2019-8699/index.md","name":"CVE-2019-8699","record":{"aliases":["GHSA-59j4-2v5x-m6r9"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"iOS Walkie-Talkie","requires_auth":"none","summary":"An attacker can force a recipient to answer a Walkie-Talkie connection during a phone call due to a state management logic error in iOS.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apple","cpe":[{"product":"iphone_os","vendor":"apple"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"A logic issue existed in the handling of answering phone calls. The issue was addressed with improved state management. This issue is fixed in iOS 12.4. The initiator of a phone call may be able to cause the recipient to answer a simultaneous Walkie-Talkie connection.","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":"Business logic in iOS","id":"CVE-2019-8699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apple:iphone_os","products":["apple:iphone_os"],"type":"business_logic","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in macOS","id":"CVE-2019-8701"},"packages":[],"prev":{"headline":"Security feature bypass in iOS","id":"CVE-2019-8698"},"products":["iOS"],"published":"2019-12-18","related":[{"cvss_score":8.8,"headline":"Apple iOS WebKit Buffer Overflow","id":"CVE-2021-30666","kev_date_added":"2021-11-03","published":"2021-09-08"},{"cvss_score":8.8,"headline":"Apple iOS WebKit Memory Corruption","id":"CVE-2021-30761","kev_date_added":"2021-11-03","published":"2021-09-08"},{"cvss_score":8.8,"headline":"Apple iOS WebKit Use-After-Free","id":"CVE-2021-30762","kev_date_added":"2021-11-03","published":"2021-09-08"},{"cvss_score":8.8,"headline":"Apple iOS Webkit Memory Corruption","id":"CVE-2016-4657","kev_date_added":"2022-05-24","published":"2016-08-25"},{"cvss_score":7.8,"headline":"Apple Multiple Products Memory Corruption","id":"CVE-2019-7286","kev_date_added":"2022-05-23","published":"2019-12-18"},{"cvss_score":7.8,"headline":"Apple iOS Memory Corruption","id":"CVE-2019-7287","kev_date_added":"2022-05-23","published":"2019-12-18"},{"cvss_score":7.8,"headline":"Apple Multiple Products Use-After-Free","id":"CVE-2019-8605","kev_date_added":"2022-06-27","published":"2019-12-18"}],"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":"An attacker can force a recipient to answer a Walkie-Talkie connection during a phone call due to a state management logic error in iOS.","url":"https://insights.sbomify.com/CVE-2019-8699/"}