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.
References
Link | Resource |
---|---|
https://github.com/typestack/class-validator#passing-options | Third Party Advisory |
https://github.com/typestack/class-validator/issues/1422#issuecomment-1344635415 | Issue Tracking Release Notes Third Party Advisory |
https://github.com/typestack/class-validator/issues/438 | Exploit Issue Tracking Third Party Advisory |
https://github.com/typestack/class-validator/issues/438#issuecomment-964728471 | Exploit Issue Tracking Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2019-10-24T00:00:00
Updated: 2022-12-14T00:00:00
Reserved: 2019-10-24T00:00:00
Link: CVE-2019-18413
JSON object: View
NVD Information
Status : Analyzed
Published: 2019-10-24T18:15:11.497
Modified: 2023-02-28T15:10:31.297
Link: CVE-2019-18413
JSON object: View
Redhat Information
No data.