Packages / @tootallnate/once / Security
@tootallnate/once vulnerable to Incorrect Control Flow Scoping
Affected releases · @tootallnate/once
- 3.x3.0.0Fixed in 3.0.1
- 2.x2.0.0Fixed in 2.0.1
- 1.x1.0.0 – 1.1.2No fix on this line yet
On 3.x, the newest line:
npm install @tootallnate/once@3.0.1Every release on a timeline
Affected
3.0.0
1 release
Fixed
3.0.1
1 release, latest
Affected
2.0.0
1 release
Fixed
2.0.1
1 release
Affected
1.0.0 – 1.1.2
4 releases
What happens
Versions of the package @tootallnate/once before 3.0.1 are vulnerable to Incorrect Control Flow Scoping in promise resolving when AbortSignal option is used. The Promise remains in a permanently pending state after the signal is aborted, causing any await or .then() usage to hang indefinitely. This can cause a control-flow leak that can lead to stalled requests, blocked workers, or degraded application availability.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.