CVE-2019-18413
Typestack Class-validator Project Typestack Class-validator vulnerability
In TypeStack class-validator 0.10.2, validate() input validation can be bypassed because certain internal attributes can be overwritten via a conflicting name. Even though there is an optional forbidUnknownValues parameter that can be used to reduce the risk of this bypass, this option is not documented and thus most developers configure input validation in the vulnerable default manner. With this vulnerability, attackers can launch SQL Injection or XSS attacks by injecting arbitrary malicious input. NOTE: a software maintainer agrees with the "is not documented" finding but suggests that much of the responsibility for the risk lies in a different product.
Affected products
Typestack Class-validator. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Typestack Class-validator Project Typestack Class-validator runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/typestack/class-validator#passing-options · Third Party Advisory
- github.com/typestack/class-validator/issues/1422#issuecomment-1344635415 · Third Party Advisory
- github.com/typestack/class-validator/issues/438 · Exploit
- github.com/typestack/class-validator/issues/438#issuecomment-964728471 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2019-18413
- cve.org/CVERecord?id=CVE-2019-18413
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.