{"answers":{"affected":"2 open source packages ship an affected version, including @risingstack/protect. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000160 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1000160 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1000160 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Apr 2018. 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-2018-1000160 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000160 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Apr 2018. 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-2018-1000160 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @risingstack/protect (npm): affected all versions up to 1.2.0; no fix listed\n- @risingstack/protect (npm): affected all versions up to 1.2.0; no fix listed\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-2018-1000160/ (Markdown: https://insights.sbomify.com/CVE-2018-1000160/index.md)","id":"CVE-2018-1000160","markdown":"https://insights.sbomify.com/CVE-2018-1000160/index.md","name":"CVE-2018-1000160","record":{"aliases":["GHSA-vpch-rxw3-fgx8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js XSS protection library","requires_auth":"none","summary":"The protect library incorrectly validates certain XSS strings as safe, allowing attackers to bypass XSS protections in applications using this library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"protect","vendor":"risingstack"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"RisingStack protect version 1.2.0 and earlier contains a Cross Site Scripting (XSS) vulnerability in isXss() function in lib/rules/xss.js that can result in dangerous XSS strings being validated as safe. This attack appears to be exploitable via A number of XSS strings(26) detailed in the GitHub issue #16.","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":false,"headline":"Cross-Site Scripting in @risingstack/protect","id":"CVE-2018-1000160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2018-1000161"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.2.0"],"package":"@risingstack/protect","purl":null,"source":"GHSA-vpch-rxw3-fgx8"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.2.0"],"package":"@risingstack/protect","purl":"pkg:npm/%40risingstack/protect","source":"GHSA-vpch-rxw3-fgx8"}],"prev":{"headline":"tlslite-ng off-by-one error on mac checking","id":"CVE-2018-1000159"},"products":["n/a"],"published":"2018-04-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-05","vendors":["n/a"]},"summary":"The protect library incorrectly validates certain XSS strings as safe, allowing attackers to bypass XSS protections in applications using this library.","url":"https://insights.sbomify.com/CVE-2018-1000160/"}