{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2016-0182 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-0182 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-0182 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 11 May 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-0182 and fix it if it is affected.\n\nWhat it is: CVE-2016-0182 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 11 May 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-0182 in the wild and no public exploit code.\n\nAffected product: Microsoft Windows 10. 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-0182/ (Markdown: https://insights.sbomify.com/CVE-2016-0182/index.md)","id":"CVE-2016-0182","markdown":"https://insights.sbomify.com/CVE-2016-0182/index.md","name":"CVE-2016-0182","record":{"aliases":["GHSA-5qhv-625r-3h5r"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows Journal","requires_auth":"none","summary":"Remote attackers can execute arbitrary code by tricking users into opening a crafted Windows Journal file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"windows_10","vendor":"microsoft"},{"product":"windows_7","vendor":"microsoft"},{"product":"windows_8.1","vendor":"microsoft"},{"product":"windows_rt_8.1","vendor":"microsoft"},{"product":"windows_vista","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Windows Journal in Microsoft Windows Vista SP2, Windows 7 SP1, Windows 8.1, Windows RT 8.1, and Windows 10 Gold and 1511 allows remote attackers to execute arbitrary code via a crafted Journal (aka .jnt) file, aka \"Windows Journal Memory Corruption Vulnerability.\"","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":"Memory corruption in n/a","id":"CVE-2016-0182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:windows_10","products":["microsoft:windows_10","microsoft:windows_7","microsoft:windows_8.1","microsoft:windows_rt_8.1","microsoft:windows_vista"],"type":"memory_corruption","year":"2016"},"n_packages":0,"n_references":4,"next":{"headline":"Code injection in n/a","id":"CVE-2016-0183"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2016-0181"},"products":["n/a"],"published":"2016-05-11","related":[{"cvss_score":8.8,"headline":"Microsoft Windows Adobe Type Manager Library Remote Code Execution","id":"CVE-2015-2426","kev_date_added":"2022-03-28","published":"2015-07-20"},{"cvss_score":6.6,"headline":"Microsoft Windows Mount Manager Privilege Escalation","id":"CVE-2015-1769","kev_date_added":"2022-05-25","published":"2015-08-15"},{"cvss_score":10,"headline":"Windows Hard Link Elevation of Privilege Vulnerability","id":"CVE-2020-1467","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":9.9,"headline":"Windows TCP/IP Remote Code Execution Vulnerability","id":"CVE-2021-26424","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":9.9,"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2021-28476","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":9.9,"headline":"Windows Hyper-V Remote Code Execution Vulnerability","id":"CVE-2021-26867","kev_date_added":null,"published":"2021-03-11"},{"cvss_score":9.9,"headline":"Security feature bypass in Windows","id":"CVE-2019-1384","kev_date_added":null,"published":"2019-11-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-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by tricking users into opening a crafted Windows Journal file.","url":"https://insights.sbomify.com/CVE-2016-0182/"}