{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-1849 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-1849 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-1849 is a low-severity vulnerability in Apple Iphone Os, published on 20 May 2016. 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-2016-1849 and fix it if it is affected.\n\nWhat it is: CVE-2016-1849 is a low-severity vulnerability in Apple Iphone Os, published on 20 May 2016. 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-2016-1849 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-2016-1849/ (Markdown: https://insights.sbomify.com/CVE-2016-1849/index.md)","id":"CVE-2016-1849","markdown":"https://insights.sbomify.com/CVE-2016-1849/index.md","name":"CVE-2016-1849","record":{"aliases":["GHSA-wmg4-hccw-9xwx"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Apple Safari browser","requires_auth":"low_privilege","summary":"Local attackers can read sensitive browsing history data due to improper deletion handling in Safari's Clear History feature.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apple","cpe":[{"product":"iphone_os","vendor":"apple"},{"product":"safari","vendor":"apple"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The \"Clear History and Website Data\" feature in Apple Safari before 9.1.1, as used in iOS before 9.3.2 and other products, mishandles the deletion of browsing history, which might allow local users to obtain sensitive information by leveraging read access to a Safari directory.","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":"Information disclosure in n/a","id":"CVE-2016-1849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apple:iphone_os","products":["apple:iphone_os","apple:safari"],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-1850"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2016-1848"},"products":["n/a"],"published":"2016-05-20","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can read sensitive browsing history data due to improper deletion handling in Safari's Clear History feature.","url":"https://insights.sbomify.com/CVE-2016-1849/"}