First published: Thu Oct 24 2019(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Typestack Class-validator Project Typestack Class-validator | =0.10.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2019-18413 is critical with a severity value of 9.8.
TypeStack class-validator is a library used for input validation in TypeScript applications.
The vulnerability in TypeStack class-validator 0.10.2 allows a remote attacker to bypass security restrictions by overwriting certain internal attributes.
To reduce the risk of the bypass, the optional forbidUnknownValues parameter can be used during validation.
More information about CVE-2019-18413 can be found on the following references: [link1](https://exchange.xforce.ibmcloud.com/vulnerabilities/170114), [link2](https://www.ibm.com/support/pages/node/6557106), [link3](https://github.com/typestack/class-validator#passing-options).