Technical impact
Seroval is a JavaScript library for serializing complex structures. Before version 1.6.8, the deserialization routine could reconstruct an AsyncIteratorFactoryInstance by arbitrarily calling source.on(listener) without checking that the supplied source was a legitimate internal stream. An attacker who supplies crafted Seroval data can create an object that defines a callable value or an on method. By reusing an identifier during deserialization, the library will invoke the attacker‑generated function, potentially executing arbitrary code in the application’s context. This flaw is a type of insecure deserialization (CWE‑502) and can lead to confidentiality, integrity, or availability loss depending on the behavior that the plugin implements.
Affected Systems
The vulnerability appears in the lxsmnsyc:seroval library prior to version 1.6.8. Any application that uses an older Seroval release and accepts untrusted serialized input, especially if it includes custom plugins or callbacks, is vulnerable. The issue is addressed in seroval release 1.6.8 and later versions.
Risk and Exploitability
With a CVSS score of 7.3, the flaw presents a moderate to high severity risk. No EPSS data is available and the vulnerability is not listed in the CISA KEV catalog. The attack requires an attacker to supply malicious serialized data, and based on the description, it is inferred that this data could reach an application using Seroval if the application accepts external serialized input. Once processed, the attacker’s callable can execute within the application’s context, potentially allowing full control within the bounds of the plugin’s permissions. Because the flaw lies in deserialization, the exploitation path is well understood and likely to be automated in future tools.
Github GHSA