{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-16855 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16855 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16855 is a medium-severity vulnerability in Microsoft Office, published on 11 Sep 2020. 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-2020-16855 and fix it if it is affected.\n\nWhat it is: CVE-2020-16855 is a medium-severity vulnerability in Microsoft Office, published on 11 Sep 2020. 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-2020-16855 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-2020-16855/ (Markdown: https://insights.sbomify.com/CVE-2020-16855/index.md)","id":"CVE-2020-16855","markdown":"https://insights.sbomify.com/CVE-2020-16855/index.md","name":"CVE-2020-16855","record":{"aliases":["GHSA-gwjj-xwgr-2v6f"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Microsoft Office","requires_auth":"none","summary":"An attacker can view out-of-bounds memory contents by tricking a user into opening a specially crafted file in Microsoft Office.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"office","vendor":"microsoft"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"\u003cp\u003eAn information disclosure vulnerability exists when Microsoft Office software reads out of bound memory due to an uninitialized variable, which could disclose the contents of memory. An attacker who successfully exploited the vulnerability could view out of bound memory.\u003c/p\u003e\n\u003cp\u003eExploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Office software.\u003c/p\u003e\n\u003cp\u003eThe security update addresses the vulnerability by properly initializing the affected variable.\u003c/p\u003e","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":"Microsoft Office Information Disclosure Vulnerability","id":"CVE-2020-16855","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:office","products":["microsoft:office"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Visual Studio Remote Code Execution Vulnerability","id":"CVE-2020-16856"},"packages":[],"prev":{"headline":"Windows Kernel Information Disclosure Vulnerability","id":"CVE-2020-16854"},"products":["Microsoft Office 2016 for Mac","Microsoft Office 2019 for Mac"],"published":"2020-09-11","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":"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-04","vendors":["Microsoft"]},"summary":"An attacker can view out-of-bounds memory contents by tricking a user into opening a specially crafted file in Microsoft Office.","url":"https://insights.sbomify.com/CVE-2020-16855/"}