{"answers":{"affected":"2 open source packages ship an affected version, including striptags. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32696 in the wild and no public exploit code.","fix":"Upgrade striptags to 3.2.0 or later.","what":"CVE-2021-32696 is a low-severity cross-site scripting vulnerability in ericnorris striptags, published on 18 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32696 and fix it if it is affected.\n\nWhat it is: CVE-2021-32696 is a low-severity cross-site scripting vulnerability in ericnorris striptags, published on 18 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32696 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- striptags (npm): affected all versions; fixed in 3.2.0\n- striptags (npm): affected all versions; fixed in 3.2.0\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-2021-32696/ (Markdown: https://insights.sbomify.com/CVE-2021-32696/index.md)","id":"CVE-2021-32696","markdown":"https://insights.sbomify.com/CVE-2021-32696/index.md","name":"CVE-2021-32696","record":{"aliases":["GHSA-qxg5-2qff-p49r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm striptags library","requires_auth":"none","summary":"Attackers can trigger XSS in applications using striptags by passing array-like objects, bypassing sanitization via type confusion.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"striptags","vendor":"striptags_project"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-241","name":"Improper Handling of Unexpected Data Type"}],"description":"The npm package \"striptags\" is an implementation of PHP's strip_tags in Typescript. In striptags before version 3.2.0, a type-confusion vulnerability can cause `striptags` to concatenate unsanitized strings when an array-like object is passed in as the `html` parameter. This can be abused by an attacker who can control the shape of their input, e.g. if query parameters are passed directly into the function. This can lead to a XSS.","ecosystems":["npm"],"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":"Passing in a non-string 'html' argument can lead to unsanitized output","id":"CVE-2021-32696","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2021"},"n_packages":2,"n_references":4,"next":{"headline":"Form validation can be skipped","id":"CVE-2021-32697"},"packages":[{"ecosystem":"npm","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"striptags","purl":null,"source":"GHSA-qxg5-2qff-p49r"},{"ecosystem":"npm","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"striptags","purl":"pkg:npm/striptags","source":"GHSA-qxg5-2qff-p49r"}],"prev":{"headline":"Malicious Android app could access Shared Preferences of the Nextcloud Android client","id":"CVE-2021-32695"},"products":["striptags"],"published":"2021-06-18","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["ericnorris"]},"summary":"Attackers can trigger XSS in applications using striptags by passing array-like objects, bypassing sanitization via type confusion.","url":"https://insights.sbomify.com/CVE-2021-32696/"}