{"answers":{"affected":"It affects 3 products.","exploited":"Yes. Attackers have exploited CVE-2018-0798 in the wild since at least 3 Nov 2021.","fix":"No fix has been published for CVE-2018-0798 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.","what":"CVE-2018-0798 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Jan 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-0798 and fix it if it is affected.\n\nWhat it is: CVE-2018-0798 is a high-severity memory corruption vulnerability in Microsoft Office, published on 10 Jan 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: Yes. Attackers have exploited CVE-2018-0798 in the wild since at least 3 Nov 2021.\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-0798/ (Markdown: https://insights.sbomify.com/CVE-2018-0798/index.md)","id":"CVE-2018-0798","markdown":"https://insights.sbomify.com/CVE-2018-0798/index.md","name":"CVE-2018-0798","record":{"aliases":["GHSA-4prc-qxrc-76p6"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Office Equation Editor","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via memory corruption in the Microsoft Office Equation Editor component.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"},{"product":"office_compatibility_pack","vendor":"microsoft"},{"product":"word","vendor":"microsoft"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Equation Editor in Microsoft Office 2007, Microsoft Office 2010, Microsoft Office 2013, and Microsoft Office 2016 allows a remote code execution vulnerability due to the way objects are handled in memory, aka \"Microsoft Office Memory Corruption Vulnerability\".","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-08-19","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-08-19T02:17:50Z","kind":"github_poc","ref":"https://github.com/Sunqiz/CVE-2018-0798-reproduction","stars":0,"title":"CVE-2018-0798复现"}],"tier":"exploited"},"has_fix":null,"headline":"Microsoft Office Memory Corruption","id":"CVE-2018-0798","indexable":true,"kev":{"dateAdded":"2021-11-03","dueDate":"2022-05-03","knownRansomwareCampaignUse":"Unknown","product":"Office","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Microsoft","vulnerabilityName":"Microsoft Office Memory Corruption Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office","microsoft:office_compatibility_pack","microsoft:word"],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in Microsoft Access","id":"CVE-2018-0799"},"packages":[],"prev":{"headline":"Memory corruption in Microsoft Office","id":"CVE-2018-0797"},"products":["Equation Editor"],"published":"2018-01-10","related":[{"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"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":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Microsoft Corporation"]},"summary":"Remote attackers can execute arbitrary code via memory corruption in the Microsoft Office Equation Editor component.","url":"https://insights.sbomify.com/CVE-2018-0798/"}