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.
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
| Link | Tags |
|---|---|
| https://github.com/typestack/class-validator/issues/438 | issue tracking exploit third party advisory |
| https://github.com/typestack/class-validator#passing-options | third party advisory |
| https://github.com/typestack/class-validator/issues/438#issuecomment-964728471 | issue tracking exploit third party advisory |
| https://github.com/typestack/class-validator/issues/1422#issuecomment-1344635415 | issue tracking release notes third party advisory |