NetSight
high8.2No CVE yet

GHSA-x5rw-q4pp-hg5g

devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

Impact

When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned `stringifyAsync` promise. Under Node's default unhandled-rejection behavior this can terminate the process. Applications whose asynchronous failures/timing can be influenced by requests are potentially exposed. This is essentially impossible to exploit, and is much more likely to surface as a developer-introduced bug.

An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of outages.

Affected packages

EcosystemPackageAffectedFixed in
npmdevalue>= 5.8.0, <= 5.9.25.9.3

Weakness classification

References