{"answers":{"affected":"4 open source packages ship an affected version, including typo3/html-sanitizer. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-38500 in the wild and no public exploit code.","fix":"Upgrade typo3/html-sanitizer to a fixed version for your release line: 1.5.1 or 2.1.2.","what":"CVE-2023-38500 is a medium-severity cross-site scripting vulnerability in TYPO3 html-sanitizer, published on 25 Jul 2023. 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-2023-38500 and fix it if it is affected.\n\nWhat it is: CVE-2023-38500 is a medium-severity cross-site scripting vulnerability in TYPO3 html-sanitizer, published on 25 Jul 2023. 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-2023-38500 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- typo3/html-sanitizer (Packagist): affected from 1.0.0; fixed in 1.5.1\n- typo3/html-sanitizer (Packagist): affected from 1.0.0; fixed in 1.5.1\n- typo3/html-sanitizer (Packagist): affected from 2.0.0; fixed in 2.1.2\n- typo3/html-sanitizer (Packagist): affected from 2.0.0; fixed in 2.1.2\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-2023-38500/ (Markdown: https://insights.sbomify.com/CVE-2023-38500/index.md)","id":"CVE-2023-38500","markdown":"https://insights.sbomify.com/CVE-2023-38500/index.md","name":"CVE-2023-38500","record":{"aliases":["GHSA-59jf-3q9v-rh6g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"PHP HTML Sanitizer","requires_auth":"none","summary":"Attackers can bypass XSS protection in TYPO3 HTML Sanitizer via malicious markup in noscript elements when that feature is enabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"html_sanitizer","vendor":"typo3"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/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":"TYPO3 HTML Sanitizer is an HTML sanitizer, written in PHP, aiming to provide cross-site-scripting-safe markup based on explicitly allowed tags, attributes and values. Starting in version 1.0.0 and prior to versions 1.5.1 and 2.1.2, due to an encoding issue in the serialization layer, malicious markup nested in a `noscript` element was not encoded correctly. `noscript` is disabled in the default configuration, but might have been enabled in custom scenarios. This allows bypassing the cross-site scripting mechanism of TYPO3 HTML Sanitizer. Versions 1.5.1 and 2.1.2 fix the problem.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"By-passing Cross-Site Scripting Protection in HTML Sanitizer","id":"CVE-2023-38500","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"xss","year":"2023"},"n_packages":4,"n_references":3,"next":{"headline":"copyparty vulnerable to reflected cross-site scripting via k304 parameter","id":"CVE-2023-38501"},"packages":[{"ecosystem":"Packagist","fixed":["1.5.1"],"introduced":["1.0.0"],"last_affected":[],"package":"typo3/html-sanitizer","purl":null,"source":"GHSA-59jf-3q9v-rh6g"},{"ecosystem":"Packagist","fixed":["1.5.1"],"introduced":["1.0.0"],"last_affected":[],"package":"typo3/html-sanitizer","purl":"pkg:composer/typo3/html-sanitizer","source":"GHSA-59jf-3q9v-rh6g"},{"ecosystem":"Packagist","fixed":["2.1.2"],"introduced":["2.0.0"],"last_affected":[],"package":"typo3/html-sanitizer","purl":null,"source":"GHSA-59jf-3q9v-rh6g"},{"ecosystem":"Packagist","fixed":["2.1.2"],"introduced":["2.0.0"],"last_affected":[],"package":"typo3/html-sanitizer","purl":"pkg:composer/typo3/html-sanitizer","source":"GHSA-59jf-3q9v-rh6g"}],"prev":{"headline":"typo3/cms-core Information Disclosure due to Out-of-scope Site Resolution","id":"CVE-2023-38499"},"products":["html-sanitizer"],"published":"2023-07-25","related":[{"cvss_score":6.1,"headline":"Cross-Site Scripting Protection bypass in HTML Sanitizer","id":"CVE-2022-23499","kev_date_added":null,"published":"2022-12-13"},{"cvss_score":6.1,"headline":"Bypass of Cross-Site Scripting Protection in typo3/html-sanitizer","id":"CVE-2022-36020","kev_date_added":null,"published":"2022-09-13"},{"cvss_score":4.7,"headline":"By-passing Cross-Site Scripting Protection in HTML Sanitizer","id":"CVE-2023-47125","kev_date_added":null,"published":"2023-11-14"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-10","vendors":["TYPO3"]},"summary":"Attackers can bypass XSS protection in TYPO3 HTML Sanitizer via malicious markup in noscript elements when that feature is enabled.","url":"https://insights.sbomify.com/CVE-2023-38500/"}