Description
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.
Remediation
References
https://github.com/typestack/class-validator#passing-options
https://github.com/typestack/class-validator/issues/1422#issuecomment-1344635415
https://github.com/typestack/class-validator/issues/438
https://github.com/typestack/class-validator/issues/438#issuecomment-964728471
Related Vulnerabilities
CVE-2018-16462 Vulnerability in npm package apex-publish-static-files
CVE-2022-24718 Vulnerability in npm package @finastra/ssr-pages
CVE-2022-24846 Vulnerability in maven package org.geowebcache:gwc-diskquota-jdbc
CVE-2021-21165 Vulnerability in maven package org.webjars.npm:electron
CVE-2019-16572 Vulnerability in maven package org.jenkins-ci.plugins:weibo