LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000232: NodeJS Tough-Cookie version 2.2.2 contains a Regular Expression Parsing vulnerability in HTTP request Cooki...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects tough-cookie, a Node.js cookie parsing library. Version 2.2.2 can consume excessive processing time while parsing a client-supplied Cookie header, causing denial of service. The bundle says the issue was fixed in version 2.3.0.

Executive priority

Treat this as an availability risk, not confirmed data theft or code execution. Prioritize remediation for public-facing Node.js services or vendor appliances using the affected dependency, especially where downtime would disrupt customer access or operations.

Technical view

CVE-2016-1000232 is a regular expression parsing issue in tough-cookie 2.2.2 during HTTP Cookie header parsing. A specially crafted custom Cookie header can trigger denial of service. Sources identify the fix as tough-cookie 2.3.0; no CVSS, CWE, or complete product matrix is provided.

Likely exposure

Exposure is most likely in Node.js applications or vendor products that bundle tough-cookie 2.2.2 and parse untrusted HTTP Cookie headers. Public web services are the main concern because clients can supply Cookie headers directly.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It describes exploitability through a custom HTTP header passed by a client, with impact limited to denial of service based on the provided evidence.

Researcher notes

Evidence is concise but consistent: affected version 2.2.2, vulnerable surface is HTTP Cookie header parsing, impact is denial of service, and fix is 2.3.0. The bundle lacks CVSS, CWE, proof of exploitation, and a full affected-product inventory.

Mitigation direction

  • Upgrade tough-cookie from 2.2.2 to 2.3.0 or later.
  • Apply vendor fixes for bundled products such as IBM or Red Hat packages where applicable.
  • Inventory dependency trees and SBOMs for transitive tough-cookie 2.2.2 usage.
  • Prioritize internet-facing services that parse client Cookie headers.
  • Review vendor advisories before choosing compensating controls.

Validation and detection

  • Check application manifests, lockfiles, and SBOMs for tough-cookie 2.2.2.
  • Confirm deployed artifacts resolve tough-cookie to 2.3.0 or later.
  • Review vendor advisory status for IBM API Connect and Red Hat packages.
  • Identify public routes that process untrusted Cookie headers.
  • Monitor affected services for abnormal CPU saturation or request handling delays.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-1000232 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.