Jsdom version 0.5.5 introduces subtle dependency version constraints compared to its predecessor, version 0.5.4, potentially affecting developers managing their project's dependencies. Key updates involve CSSOM, CSSStyle, NWMatcher, and Contextify. Version 0.5.5 specifically pins CSSOM to "~0.2.5," CSSStyle to "~0.2.3," NWMatcher to "~1.3.1," and Contextify to "~0.1.5," indicating a preference for patch updates within those minor versions. In contrast, version 0.5.4 uses more flexible ranges like "0.2.x" for CSSOM, ">=0.2.3" for CSSStyle, ">=1.3.1" for NWMatcher and "0.1.x" for Contextify, allowing for a broader range of compatible versions including potentially breaking minor releases. Both versions maintain identical major dependencies on "request" (2.x) and "htmlparser" (1.x).
In the devDependencies, version 0.5.5 has pinned the versions of nodeunit to "~0.8.0" while 0.5.4 defined ">=0.5.x".
Developers upgrading from 0.5.4 should carefully evaluate these changes, paying close attention to the dependency constraints. The tighter constraints in 0.5.5 could resolve specific bugs or ensure compatibility with a specific set of dependency versions but may also introduce conflicts if your project relies on versions outside these ranges. Both versions offer a robust JavaScript implementation of the W3C DOM, ideal for server-side testing or manipulating web content in Node.js environments. The choice between versions hinges on the developer's need for specific dependency versions versus the flexibility afforded by broader version ranges. Version 0.5.5 was released on March 29, 2013, just a few days after version 0.5.4 on March 24, 2013.
All the vulnerabilities related to the version 0.5.5 of the package
Server-Side Request Forgery in Request
The request package through 2.88.2 for Node.js and the @cypress/request package prior to 3.0.0 allow a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP).
NOTE: The request package is no longer supported by the maintainer.
form-data uses unsafe random function in form-data for choosing boundary
form-data uses Math.random() to select a boundary value for multipart form-encoded data. This can lead to a security issue if an attacker:
Because the values of Math.random() are pseudo-random and predictable (see: https://blog.securityevaluators.com/hacking-the-javascript-lottery-80cc437e3b7f), an attacker who can observe a few sequential values can determine the state of the PRNG and predict future values, includes those used to generate form-data's boundary value. The allows the attacker to craft a value that contains a boundary value, allowing them to inject additional parameters into the request.
This is largely the same vulnerability as was recently found in undici by parrot409 -- I'm not affiliated with that researcher but want to give credit where credit is due! My PoC is largely based on their work.
The culprit is this line here: https://github.com/form-data/form-data/blob/426ba9ac440f95d1998dac9a5cd8d738043b048f/lib/form_data.js#L347
An attacker who is able to predict the output of Math.random() can predict this boundary value, and craft a payload that contains the boundary value, followed by another, fully attacker-controlled field. This is roughly equivalent to any sort of improper escaping vulnerability, with the caveat that the attacker must find a way to observe other Math.random() values generated by the application to solve for the state of the PRNG. However, Math.random() is used in all sorts of places that might be visible to an attacker (including by form-data itself, if the attacker can arrange for the vulnerable application to make a request to an attacker-controlled server using form-data, such as a user-controlled webhook -- the attacker could observe the boundary values from those requests to observe the Math.random() outputs). A common example would be a x-request-id header added by the server. These sorts of headers are often used for distributed tracing, to correlate errors across the frontend and backend. Math.random() is a fine place to get these sorts of IDs (in fact, opentelemetry uses Math.random for this purpose)
PoC here: https://github.com/benweissmann/CVE-2025-7783-poc
Instructions are in that repo. It's based on the PoC from https://hackerone.com/reports/2913312 but simplified somewhat; the vulnerable application has a more direct side-channel from which to observe Math.random() values (a separate endpoint that happens to include a randomly-generated request ID).
For an application to be vulnerable, it must:
form-data to send data including user-controlled data to some other system. The attacker must be able to do something malicious by adding extra parameters (that were not intended to be user-controlled) to this request. Depending on the target system's handling of repeated parameters, the attacker might be able to overwrite values in addition to appending values (some multipart form handlers deal with repeats by overwriting values instead of representing them as an array)If an application is vulnerable, this allows an attacker to make arbitrary requests to internal systems.
tough-cookie Prototype Pollution vulnerability
Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. This issue arises from the manner in which the objects are initialized.
Regular Expression Denial of Service
A Regular Expression vulnerability was found in nwmatcher before 1.4.4. The fix replacing multiple repeated instances of the "\s*" pattern.