{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-0697 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-0697 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-0697 is a high-severity vulnerability in Microsoft Office 365 Proplus, published on 11 Feb 2020. 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-2020-0697 and fix it if it is affected.\n\nWhat it is: CVE-2020-0697 is a high-severity vulnerability in Microsoft Office 365 Proplus, published on 11 Feb 2020. 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-2020-0697 in the wild and no public exploit code.\n\nAffected product: Microsoft Office 365 Proplus. 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-2020-0697/ (Markdown: https://insights.sbomify.com/CVE-2020-0697/index.md)","id":"CVE-2020-0697","markdown":"https://insights.sbomify.com/CVE-2020-0697/index.md","name":"CVE-2020-0697","record":{"aliases":["GHSA-2cgq-hh5m-vc66"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office","requires_auth":"low_privilege","summary":"An authenticated attacker can escalate privileges to SYSTEM by placing a crafted file, enabling arbitrary file corruption in Microsoft Office.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office_365_proplus","vendor":"microsoft"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An elevation of privilege vulnerability exists in Microsoft Office OLicenseHeartbeat task, where an attacker who successfully exploited this vulnerability could run this task as SYSTEM.To exploit the vulnerability, an authenticated attacker would need to place a specially crafted file in a specific location, thereby allowing arbitrary file corruption.The security update addresses the vulnerability by correcting how the process validates the log file., aka 'Microsoft Office Tampering 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 Office 365 ProPlus","id":"CVE-2020-0697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office_365_proplus","products":["microsoft:office_365_proplus"],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Windows","id":"CVE-2020-0698"},"packages":[],"prev":{"headline":"Security feature bypass in Microsoft Office","id":"CVE-2020-0696"},"products":["Office 365 ProPlus"],"published":"2020-02-11","related":[{"cvss_score":8.8,"headline":"Memory corruption in Office 365 ProPlus","id":"CVE-2020-0979","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":8.8,"headline":"Code injection in Microsoft Office","id":"CVE-2018-8582","kev_date_added":null,"published":"2018-11-14"},{"cvss_score":7.8,"headline":"Memory corruption in Office 365 ProPlus","id":"CVE-2020-0653","kev_date_added":null,"published":"2020-01-14"},{"cvss_score":7.8,"headline":"Memory corruption in Microsoft Project","id":"CVE-2018-8575","kev_date_added":null,"published":"2018-11-14"}],"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-08-04","vendors":["Microsoft"]},"summary":"An authenticated attacker can escalate privileges to SYSTEM by placing a crafted file, enabling arbitrary file corruption in Microsoft Office.","url":"https://insights.sbomify.com/CVE-2020-0697/"}