{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2019-6207 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6207 is a medium-severity vulnerability in Apple Iphone Os, published on 18 Dec 2019. 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-2019-6207 and fix it if it is affected.\n\nWhat it is: CVE-2019-6207 is a medium-severity vulnerability in Apple Iphone Os, published on 18 Dec 2019. 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-2019-6207 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-6207/ (Markdown: https://insights.sbomify.com/CVE-2019-6207/index.md)","id":"CVE-2019-6207","markdown":"https://insights.sbomify.com/CVE-2019-6207/index.md","name":"CVE-2019-6207","record":{"aliases":["GHSA-8m2g-hqw3-95cp"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Apple OS","requires_auth":"low_privilege","summary":"A malicious application can determine kernel memory layout due to an out-of-bounds read vulnerability in Apple operating systems.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apple","cpe":[{"product":"iphone_os","vendor":"apple"},{"product":"mac_os_x","vendor":"apple"},{"product":"tvos","vendor":"apple"},{"product":"watchos","vendor":"apple"}],"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-125","name":"Out-of-bounds Read"}],"description":"An out-of-bounds read issue existed that led to the disclosure of kernel memory. This was addressed with improved input validation. This issue is fixed in iOS 12.2, macOS Mojave 10.14.4, tvOS 12.2, watchOS 5.2. A malicious application may be able to determine kernel memory layout.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-05-17","github_poc":3,"max_poc_stars":69,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-05-17T06:37:07Z","kind":"github_poc","ref":"https://github.com/maldiohead/CVE-2019-6207","stars":69,"title":"xnu kernel  heap  info leak"},{"date":"2020-04-10T14:30:16Z","kind":"github_poc","ref":"https://github.com/DimitriFourny/cve-2019-6207","stars":29,"title":"MacOS kernel memory leak (4 bytes)"},{"date":"2019-05-17T06:17:51Z","kind":"github_poc","ref":"https://github.com/dothanthitiendiettiende/CVE-2019-6207","stars":0,"title":"getdirentriesattr  kernel  heap  inofo leak"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in iOS","id":"CVE-2019-6207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apple:iphone_os","products":["apple:iphone_os","apple:mac_os_x","apple:tvos","apple:watchos"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in iOS","id":"CVE-2019-6208"},"packages":[],"prev":{"headline":"Information disclosure in iOS","id":"CVE-2019-6206"},"products":["iOS","macOS","tvOS","watchOS"],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Apple"]},"summary":"A malicious application can determine kernel memory layout due to an out-of-bounds read vulnerability in Apple operating systems.","url":"https://insights.sbomify.com/CVE-2019-6207/"}