seroval npm Package Type Confusion Issue: Early Warning
An early warning has been issued regarding a type confusion issue in the seroval npm package versions prior to 1.5.3, which could potentially allow attacker-controlled deserialization side effects.
What happened
Reportedly, a type confusion issue in the `seroval.fromJSON()` function allows attacker-controlled JSON input to cause Promise control nodes to operate on values from the general deserialization reference table without verifying that those values are genuine internal promise resolver records. This could potentially allow attacker-controlled deserialization side effects.
The issue is under investigation and has been tracked with the ID GHSA-MV8W-475R-VWQW. The recommended action for those affected is to upgrade to `seroval@1.5.3` or later.
For more detailed information, primary sources should be consulted. The severity of this issue is currently classified as high.
How 0Day mitigates this
seroval is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.