CVE-2019-18413
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
class-validatornpm | < 0.14.0 | 0.14.0 |
Affected products
3- cpe:2.3:a:typestack_class-validator_project:typestack_class-validator:0.10.2:*:*:*:*:*:*:*
- TypeStack/class-validatordescription
Patches
Vulnerability mechanics
References
6- github.com/typestack/class-validator/issues/438nvdExploitIssue TrackingThird Party AdvisoryWEB
- github.com/typestack/class-validator/issues/438nvdExploitIssue TrackingThird Party AdvisoryWEB
- github.com/advisories/GHSA-fj58-h2fr-3pp2ghsaADVISORY
- github.com/typestack/class-validator/issues/1422nvdIssue TrackingRelease NotesThird Party AdvisoryWEB
- nvd.nist.gov/vuln/detail/CVE-2019-18413ghsaADVISORY
- github.com/typestack/class-validator/pull/1798ghsaWEB
News mentions
0No linked articles in our index yet.