{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-0850 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-0850 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-0850 is a medium-severity vulnerability in Microsoft Office, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-0850 and fix it if it is affected.\n\nWhat it is: CVE-2018-0850 is a medium-severity vulnerability in Microsoft Office, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-0850 in the wild and no public exploit code.\n\nAffected product: Microsoft Office. 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-2018-0850/ (Markdown: https://insights.sbomify.com/CVE-2018-0850/index.md)","id":"CVE-2018-0850","markdown":"https://insights.sbomify.com/CVE-2018-0850/index.md","name":"CVE-2018-0850","record":{"aliases":["GHSA-fgf4-56m5-8934"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Outlook","requires_auth":"none","summary":"Attackers can exploit improper message format validation in Microsoft Outlook to elevate privileges on the victim's system.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"},{"product":"outlook","vendor":"microsoft"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"Microsoft Outlook 2007, Microsoft Outlook 2010, Microsoft Outlook 2013, Microsoft Outlook 2016, and Microsoft Office 2016 Click-to-Run allow an elevation of privilege vulnerability due to how the format of incoming message is validated, aka \"Microsoft Outlook Elevation of Privilege 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":"Privilege escalation in Microsoft Outlook","id":"CVE-2018-0850","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office","microsoft:outlook"],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in Microsoft Office","id":"CVE-2018-0851"},"packages":[],"prev":{"headline":"Memory corruption in Equation Editor","id":"CVE-2018-0849"},"products":["Microsoft Outlook"],"published":"2018-02-15","related":[{"cvss_score":8.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0798","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":8.8,"headline":"Microsoft Office Uninitialized Memory Use","id":"CVE-2015-1770","kev_date_added":"2022-03-28","published":"2015-06-10"},{"cvss_score":8.8,"headline":"Microsoft Word Malformed Object Pointer","id":"CVE-2006-2492","kev_date_added":"2022-06-08","published":"2006-05-20"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0802","kev_date_added":"2021-11-03","published":"2018-01-10"},{"cvss_score":7.8,"headline":"Microsoft Office Memory Corruption","id":"CVE-2017-11882","kev_date_added":"2021-11-03","published":"2017-11-15"},{"cvss_score":7.8,"headline":"Microsoft Office Remote Code Execution","id":"CVE-2017-8570","kev_date_added":"2022-02-25","published":"2017-07-11"},{"cvss_score":7.8,"headline":"Microsoft Office Use-After-Free","id":"CVE-2017-0261","kev_date_added":"2022-03-03","published":"2017-05-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Microsoft Corporation"]},"summary":"Attackers can exploit improper message format validation in Microsoft Outlook to elevate privileges on the victim's system.","url":"https://insights.sbomify.com/CVE-2018-0850/"}