CVE-2019-18413: XSS
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.
Other sources
TypeStack class-validator could allow a remote attacker to bypass security restrictions, caused by a flaw in the class-validator function. By sending a specially-crafted input, an attacker could exploit this vulnerability to bypass the class-validator to perform SQL Injection or XSS attacks.
— IBM
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-18413?
The severity of CVE-2019-18413 is critical with a severity value of 9.8.
What is TypeStack class-validator?
TypeStack class-validator is a library used for input validation in TypeScript applications.
What is the vulnerability in TypeStack class-validator 0.10.2?
The vulnerability in TypeStack class-validator 0.10.2 allows a remote attacker to bypass security restrictions by overwriting certain internal attributes.
How can the bypass of input validation be prevented in TypeStack class-validator 0.10.2?
To reduce the risk of the bypass, the optional forbidUnknownValues parameter can be used during validation.
Where can I find more information about CVE-2019-18413?
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).