{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-16969 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-16969 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-16969 is a high-severity vulnerability in Microsoft Exchange Server, published on 16 Oct 2020. 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-2020-16969 and fix it if it is affected.\n\nWhat it is: CVE-2020-16969 is a high-severity vulnerability in Microsoft Exchange Server, published on 16 Oct 2020. 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-2020-16969 in the wild and no public exploit code.\n\nAffected product: Microsoft Exchange Server. 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-16969/ (Markdown: https://insights.sbomify.com/CVE-2020-16969/index.md)","id":"CVE-2020-16969","markdown":"https://insights.sbomify.com/CVE-2020-16969/index.md","name":"CVE-2020-16969","record":{"aliases":["GHSA-hx67-2mh4-8cj2"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Exchange Server","requires_auth":"none","summary":"An attacker can exploit token validation flaws in Microsoft Exchange to disclose user information via specially crafted OWA messages.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"exchange_server","vendor":"microsoft"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L/E:P/RL:O/RC:C","version":"3.1"},"cwes":[],"description":"\u003cp\u003eAn information disclosure vulnerability exists in how Microsoft Exchange validates tokens when handling certain messages. An attacker who successfully exploited the vulnerability could use this to gain further information from a user.\u003c/p\u003e\n\u003cp\u003eTo exploit the vulnerability, an attacker could include specially crafted OWA messages that could be loaded, without warning or filtering, from the attacker-controlled URL. This callback vector provides an information disclosure tactic used in web beacons and other types of tracking systems.\u003c/p\u003e\n\u003cp\u003eThe security update corrects the way that Exchange handles these token validations.\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 Exchange Information Disclosure Vulnerability","id":"CVE-2020-16969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:exchange_server","products":["microsoft:exchange_server"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Azure Sphere Unsigned Code Execution Vulnerability","id":"CVE-2020-16970"},"packages":[],"prev":{"headline":"Windows Camera Codec Pack Remote Code Execution Vulnerability","id":"CVE-2020-16968"},"products":["Microsoft Exchange Server 2013 Cumulative Update 23","Microsoft Exchange Server 2016 Cumulative Update 17","Microsoft Exchange Server 2016 Cumulative Update 18","Microsoft Exchange Server 2019 Cumulative Update 6","Microsoft Exchange Server 2019 Cumulative Update 7"],"published":"2020-10-16","related":[{"cvss_score":9.8,"headline":"Microsoft Exchange Server Privilege Escalation","id":"CVE-2024-21410","kev_date_added":"2024-02-15","published":"2024-02-13"},{"cvss_score":9.1,"headline":"Microsoft Exchange Server Remote Code Execution","id":"CVE-2021-34473","kev_date_added":"2021-11-03","published":"2021-07-14"},{"cvss_score":9.1,"headline":"Microsoft Exchange Server Remote Code Execution","id":"CVE-2021-26855","kev_date_added":"2021-11-03","published":"2021-03-02"},{"cvss_score":9,"headline":"Microsoft Exchange Server Privilege Escalation","id":"CVE-2021-34523","kev_date_added":"2021-11-03","published":"2021-07-14"},{"cvss_score":8.8,"headline":"Microsoft Exchange Server Deserialization of Untrusted Data","id":"CVE-2023-21529","kev_date_added":"2026-04-13","published":"2023-02-14"},{"cvss_score":8.8,"headline":"Microsoft Exchange Server Privilege Escalation","id":"CVE-2022-41080","kev_date_added":"2023-01-10","published":"2022-11-09"},{"cvss_score":8.8,"headline":"Microsoft Exchange Server Server-Side Request Forgery","id":"CVE-2022-41040","kev_date_added":"2022-09-30","published":"2022-10-03"}],"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 attacker can exploit token validation flaws in Microsoft Exchange to disclose user information via specially crafted OWA messages.","url":"https://insights.sbomify.com/CVE-2020-16969/"}