All reports
High

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

Affected versions

Affected versions
>= 5.8.0, <= 5.9.2
Fixed version
5.9.3

Description

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.

Links

Credits

  • elliott-with-the-longest-name-on-github