CVE-2019-18413

{"id": "CVE-2019-18413", "metrics": {"cvssMetricV2": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"version": "2.0", "baseScore": 7.5, "accessVector": "NETWORK", "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "authentication": "NONE", "integrityImpact": "PARTIAL", "accessComplexity": "LOW", "availabilityImpact": "PARTIAL", "confidentialityImpact": "PARTIAL"}, "acInsufInfo": false, "impactScore": 6.4, "baseSeverity": "HIGH", "obtainAllPrivilege": false, "exploitabilityScore": 10.0, "obtainUserPrivilege": false, "obtainOtherPrivilege": false, "userInteractionRequired": false}], "cvssMetricV31": [{"type": "Secondary", "source": "cve@mitre.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.7, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.2}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2019-10-24T18:15:11.497", "references": [{"url": "https://github.com/typestack/class-validator#passing-options", "tags": ["Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/typestack/class-validator/issues/1422#issuecomment-1344635415", "tags": ["Issue Tracking", "Release Notes", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/typestack/class-validator/issues/438", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/typestack/class-validator/issues/438#issuecomment-964728471", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/typestack/class-validator#passing-options", "tags": ["Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/typestack/class-validator/issues/1422#issuecomment-1344635415", "tags": ["Issue Tracking", "Release Notes", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/typestack/class-validator/issues/438", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/typestack/class-validator/issues/438#issuecomment-964728471", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-79"}, {"lang": "en", "value": "CWE-89"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "En TypeStack class-validator versi\u00f3n 0.10.2, la validaci\u00f3n de entrada validate() puede ser omitida porque ciertos atributos internos se pueden sobrescribir por medio de un nombre en conflicto. Aunque existe un par\u00e1metro opcional forbidUnknownValues ??que puede ser utilizado para reducir el riesgo de esta omisi\u00f3n, esta opci\u00f3n no est\u00e1 documentada y, por lo tanto, la mayor\u00eda de los desarrolladores configuran la validaci\u00f3n de entrada de una manera predeterminada vulnerable. Con esta vulnerabilidad, los atacantes pueden iniciar ataques de inyecci\u00f3n SQL o de tipo XSS mediante la inyecci\u00f3n de entradas maliciosas arbitrarias. NOTA: un mantenedor de software est\u00e1 de acuerdo con que el hallazgo \"is not documented\" pero sugiere que gran parte de la responsabilidad del riesgo recae en un producto diferente."}], "lastModified": "2024-11-21T04:33:12.760", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:typestack_class-validator_project:typestack_class-validator:0.10.2:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "6AA5A393-9873-4CC8-87CE-76E873E94526"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}