{"answers":{"affected":"2 open source packages ship an affected version, including com.mikesamuel:json-sanitizer. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-13973 in the wild and no public exploit code.","fix":"Upgrade com.mikesamuel:json-sanitizer to 1.2.1 or later.","what":"CVE-2020-13973 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jun 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-13973 and fix it if it is affected.\n\nWhat it is: CVE-2020-13973 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Jun 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-13973 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.mikesamuel:json-sanitizer (Maven): affected all versions; fixed in 1.2.1\n- com.mikesamuel:json-sanitizer (Maven): affected all versions; fixed in 1.2.1\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-13973/ (Markdown: https://insights.sbomify.com/CVE-2020-13973/index.md)","id":"CVE-2020-13973","markdown":"https://insights.sbomify.com/CVE-2020-13973/index.md","name":"CVE-2020-13973","record":{"aliases":["GHSA-g8jj-899q-8x3j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java JSON sanitizer","requires_auth":"none","summary":"An attacker can inject malicious JavaScript into web pages by exploiting a parser confusion flaw in the OWASP json-sanitizer library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"json-sanitizer","vendor":"owasp"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"OWASP json-sanitizer before 1.2.1 allows XSS. An attacker who controls a substring of the input JSON, and controls another substring adjacent to a SCRIPT element in which the output is embedded as JavaScript, may be able to confuse the HTML parser as to where the SCRIPT element ends, and cause non-script content to be interpreted as JavaScript.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2024-05-31","github_poc":2,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-05-31T00:16:57Z","kind":"github_poc","ref":"https://github.com/epicosy/json-sanitizer","stars":0,"title":"json-sanitizer with CVE-2020-13973"},{"date":"2025-08-16T13:54:26Z","kind":"github_poc","ref":"https://github.com/shoucheng3/OWASP__json-sanitizer_CVE-2020-13973_1-2-0","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Cross-site scripting in json-sanitizer","id":"CVE-2020-13973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Integer overflow in n/a","id":"CVE-2020-13974"},"packages":[{"ecosystem":"Maven","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"com.mikesamuel:json-sanitizer","purl":null,"source":"GHSA-g8jj-899q-8x3j"},{"ecosystem":"Maven","fixed":["1.2.1"],"introduced":["0"],"last_affected":[],"package":"com.mikesamuel:json-sanitizer","purl":"pkg:maven/com.mikesamuel/json-sanitizer","source":"GHSA-g8jj-899q-8x3j"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-13972"},"products":["n/a"],"published":"2020-06-09","related":[{"cvss_score":9.8,"headline":"Arbitrary code injection in json-sanitizer","id":"CVE-2021-23899","kev_date_added":null,"published":"2021-01-13"},{"cvss_score":7.5,"headline":"Uncaught Exception leading to Denial of Service in json-sanitizer","id":"CVE-2021-23900","kev_date_added":null,"published":"2021-01-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can inject malicious JavaScript into web pages by exploiting a parser confusion flaw in the OWASP json-sanitizer library.","url":"https://insights.sbomify.com/CVE-2020-13973/"}