{"answers":{"affected":"2 open source packages ship an affected version, including tough-cookie. It affects 3 products.","exploited":"There is no known exploitation of CVE-2016-1000232 in the wild and no public exploit code.","fix":"Upgrade tough-cookie to 2.3.0 or later.","what":"CVE-2016-1000232 is a medium-severity denial of service vulnerability in Ibm Api Connect, published on 5 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-1000232 and fix it if it is affected.\n\nWhat it is: CVE-2016-1000232 is a medium-severity denial of service vulnerability in Ibm Api Connect, published on 5 Sep 2018. 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-2016-1000232 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tough-cookie (npm): affected all versions; fixed in 2.3.0\n- tough-cookie (npm): affected all versions; fixed in 2.3.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-2016-1000232/ (Markdown: https://insights.sbomify.com/CVE-2016-1000232/index.md)","id":"CVE-2016-1000232","markdown":"https://insights.sbomify.com/CVE-2016-1000232/index.md","name":"CVE-2016-1000232","record":{"aliases":["CLSA-2026-1784596295","GHSA-qhv9-728r-6jqg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js cookie library","requires_auth":"none","summary":"A regular expression parsing flaw in the tough-cookie library allows attackers to cause a denial of service via crafted HTTP cookie headers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"api_connect","vendor":"ibm"},{"product":"openshift_container_platform","vendor":"redhat"},{"product":"tough-cookie","vendor":"salesforce"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cookie Header parsing that can result in Denial of Service. This attack appear to be exploitable via Custom HTTP header passed by client. This vulnerability appears to have been fixed in 2.3.0.","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":"ReDoS via long string of semicolons in tough-cookie","id":"CVE-2016-1000232","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"ibm:api_connect","products":["ibm:api_connect","redhat:openshift_container_platform"],"type":"denial_of_service","year":"2016"},"n_packages":2,"n_references":7,"next":{"headline":"cookie-signature Timing Attack","id":"CVE-2016-1000236"},"packages":[{"ecosystem":"npm","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"tough-cookie","purl":null,"source":"GHSA-qhv9-728r-6jqg"},{"ecosystem":"npm","fixed":["2.3.0"],"introduced":["0"],"last_affected":[],"package":"tough-cookie","purl":"pkg:npm/tough-cookie","source":"GHSA-qhv9-728r-6jqg"}],"prev":{"headline":"Improper Neutralization of Input During Web Page Generation in swagger-ui","id":"CVE-2016-1000229"},"products":["n/a"],"published":"2018-09-05","related":[{"cvss_score":10,"headline":"Command injection in API Connect","id":"CVE-2019-4202","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":9.8,"headline":"Authentication bypass in IBM API Connect","id":"CVE-2025-13915","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":9.8,"headline":"Command injection in API Connect","id":"CVE-2018-1469","kev_date_added":null,"published":"2018-04-04"},{"cvss_score":9.1,"headline":"IBM API Connect SQL Injection","id":"CVE-2026-9074","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":9,"headline":"Information disclosure in API Connect","id":"CVE-2019-4008","kev_date_added":null,"published":"2019-02-07"},{"cvss_score":8.9,"headline":"Server-side request forgery in API Connect","id":"CVE-2019-4203","kev_date_added":null,"published":"2019-04-15"},{"cvss_score":8.9,"headline":"Code injection in API Connect","id":"CVE-2018-1774","kev_date_added":null,"published":"2018-11-09"}],"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-06","vendors":["n/a"]},"summary":"A regular expression parsing flaw in the tough-cookie library allows attackers to cause a denial of service via crafted HTTP cookie headers.","url":"https://insights.sbomify.com/CVE-2016-1000232/"}