🚨 [security] [server] Upgrade class-validator: 0.12.2 → 0.14.0 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ class-validator (0.12.2 → 0.14.0) · Repo · Changelog

Security Advisories 🚨

🚨 SQL Injection and Cross-site Scripting in class-validator

In TypeStack class-validator, 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.

The default settings for forbidUnknownValues has been changed to true in 0.14.0.

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.

Release Notes

0.14.0 (from changelog)

Added

• add @IsTimeZone decorator to check if given string is valid IANA time zone
• add @IsISO4217CurrencyCode decorator to check if the string is an ISO 4217 currency code
• add @IsStrongPassword decorator to check if given password matches specific complexity criteria
• add @IsBase58 decorator to check if a string is base58 encoded
• add @IsTaxId decorator to check if a given string is a valid tax ID in a given locale
• add support for passing function as date generator in @MinDate and @MaxDate decorators
• add option to print constraint error message instead of constraint type in validation error
• improve decorator metadata lookup performance
• return possible values in error message for @IsEnum decorator

Fixed

• re-added @types/validator as dependency
• fix error generation when using @NestedValidation
• pass validation options correctly to validator in @IsDateString decorator
• support passing Symbol as parameter in error message generation
• specify supported locales for @IsAlphanumeric decorator
• correctly assign decorator name in metadata instead of loosing it
• fix various spelling errors in documentation
• fix various spelling errors and inconsistencies in JSDoc for decorators

Changed

• enable forbidUnknownValues option by default
• remove documentation about deprecated schema based validation and added warning
• update warning message logged about missing decorator metadata
• update libphonenumber-js to ^1.10.14 from ^1.9.43
• update various dev-dependencies

BREAKING CHANGES

forbidUnknownValues option is enabled by default

From this release the forbidUnknownValues is enabled by default. This is the desired behavior for majority of use-cases, but this change may break validation for some. The two scenarios that results in failed validation:

• when attempting to validate a class instance without metadata for it
• when using group validation and the specified validation group results in zero validation applied

The old behavior can be restored via specifying forbidUnknownValues: false option when calling the validate functions.

For more details see PR #1798 and #1422 (comment).

@NestedValidation decorator correctly assigns validation errors

Until now the errors from a nested validation in some cases were incorrectly assigned to the parent instead of the child being validated. Now the validation errors are correctly assigned.

For more details see #679.

0.13.2 (from changelog)

NOTE: This version fixes a security vulnerability allowing denial of service attacks with a specially crafted request payload. Please update as soon as possible.

Fixed

• switched to use Array.isArray in array checks from instanceof operator

Changed

• libphonenumber-js package updated to 1.9.43 from 1.9.7
• validator package updated to 13.5.2 from 13.5.2
• various dev-dependencies updated

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)