{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1195 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1195 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1195 is a low-severity path traversal vulnerability in Microsoft Edge, published on 21 May 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-1195 and fix it if it is affected.\n\nWhat it is: CVE-2020-1195 is a low-severity path traversal vulnerability in Microsoft Edge, published on 21 May 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-1195 in the wild and no public exploit code.\n\nAffected product: Microsoft Edge. 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-1195/ (Markdown: https://insights.sbomify.com/CVE-2020-1195/index.md)","id":"CVE-2020-1195","markdown":"https://insights.sbomify.com/CVE-2020-1195/index.md","name":"CVE-2020-1195","record":{"aliases":["GHSA-p4m4-hrvw-wv96"],"analysis":{"component_type":"browser","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Microsoft Edge browser","requires_auth":"none","summary":"Attackers can write files to arbitrary locations via improper input validation in the Feedback extension, leading to privilege escalation.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microsoft","cpe":[{"product":"edge","vendor":"microsoft"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An elevation of privilege vulnerability exists in Microsoft Edge (Chromium-based) when the Feedback extension improperly validates input. An attacker who successfully exploited this vulnerability could write files to arbitrary locations and gain elevated privileges.\nThe vulnerability by itself does not allow arbitrary code to run. However, this vulnerability could be used in conjunction with one or more vulnerabilities (for example a remote code execution vulnerability and another elevation of privilege vulnerability) to take advantage of the elevated privileges when running.\nThe security update addresses the vulnerability by modifying how Microsoft Edge (Chromium-based) Feedback extension validates files.","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 Edge (Chromium-based) Elevation of Privilege Vulnerability","id":"CVE-2020-1195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"microsoft:edge","products":["microsoft:edge"],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Windows","id":"CVE-2020-1196"},"packages":[],"prev":{"headline":"Denial of service in Windows","id":"CVE-2020-1194"},"products":["Microsoft Edge (Chromium-based)"],"published":"2020-05-21","related":[{"cvss_score":8.8,"headline":"Microsoft Internet Explorer Memory Corruption","id":"CVE-2021-26411","kev_date_added":"2021-11-03","published":"2021-03-11"},{"cvss_score":8.8,"headline":"Microsoft Edge Memory Corruption","id":"CVE-2016-7200","kev_date_added":"2022-03-28","published":"2016-11-10"},{"cvss_score":8.8,"headline":"Microsoft Edge Memory Corruption","id":"CVE-2016-7201","kev_date_added":"2022-03-28","published":"2016-11-10"},{"cvss_score":8.1,"headline":"Microsoft Edge and Internet Explorer Type Confusion","id":"CVE-2017-0037","kev_date_added":"2022-03-28","published":"2017-02-26"},{"cvss_score":6.5,"headline":"Microsoft Internet Explorer and Edge Information Disclosure","id":"CVE-2016-3351","kev_date_added":"2022-05-24","published":"2016-09-14"},{"cvss_score":9.8,"headline":"Memory corruption in Microsoft ChakraCore","id":"CVE-2017-0028","kev_date_added":null,"published":"2017-07-14"},{"cvss_score":9.8,"headline":"ChakraCore RCE Vulnerability","id":"CVE-2017-0223","kev_date_added":null,"published":"2017-05-15"}],"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":"2026-08-19","vendors":["Microsoft"]},"summary":"Attackers can write files to arbitrary locations via improper input validation in the Feedback extension, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2020-1195/"}