{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-15871 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-15871 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-15871 is a high-severity denial of service vulnerability in n/a, published on 24 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-15871 and fix it if it is affected.\n\nWhat it is: CVE-2017-15871 is a high-severity denial of service vulnerability in n/a, published on 24 Oct 2017. 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-2017-15871 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2017-15871/ (Markdown: https://insights.sbomify.com/CVE-2017-15871/index.md)","id":"CVE-2017-15871","markdown":"https://insights.sbomify.com/CVE-2017-15871/index.md","name":"CVE-2017-15871","record":{"aliases":["GHSA-57v2-hvjj-f26g"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript serialization library","requires_auth":"none","summary":"Attackers can cause denial of service in serialize-to-js by exploiting unsafe deserialization of malicious function strings, despite vendor warnings.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"serialize-to-js","vendor":"serialize-to-js_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"The deserialize function in serialize-to-js through 1.1.1 allows attackers to cause a denial of service via vectors involving an Immediately Invoked Function Expression \"function()\" substring, as demonstrated by a \"function(){console.log(\" call or a simple infinite loop. NOTE: the vendor agrees that denial of service can occur but notes that deserialize is explicitly listed as \"harmful\" within the README.md file","ecosystems":[],"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":"Denial of service in n/a","id":"CVE-2017-15871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-15872"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2017-15870"},"products":["n/a"],"published":"2017-10-24","related":[{"cvss_score":9.8,"headline":"Code Execution Through IIFE in serialize-to-js","id":"CVE-2017-5954","kev_date_added":null,"published":"2017-02-10"},{"cvss_score":3.1,"headline":"regular expressions Cross-Site Scripting (XSS) vulnerability in serialize-to-js","id":"CVE-2019-16772","kev_date_added":null,"published":"2019-12-06"}],"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":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can cause denial of service in serialize-to-js by exploiting unsafe deserialization of malicious function strings, despite vendor warnings.","url":"https://insights.sbomify.com/CVE-2017-15871/"}