CVE-2019-18413: Typestack Class-Validator Project vulnerability
Typestack Class-Validator Project · Typestack Class-Validator
Affected: Typestack Class-Validator Project · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 80% of scored CVEs
DescriptionCVE.org
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Cross-site Scripting
- Published
- October 2019
CoverageNo articles yet
No CyberSIXT article names CVE-2019-18413 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-79cwe.mitre.org
- github.com/typestack/class-validator/issues/438github.com
- github.com/typestack/class-validator#passing-optionsgithub.com
- github.com/typestack/class-validator/issues/438#issuecomment-964github.com
- github.com/typestack/class-validator/issues/1422#issuecomment-13github.com