Update dependency class-validator to v0.14.0 [SECURITY] #150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.12.2
->0.14.0
GitHub Vulnerability Alerts
CVE-2019-18413
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 optionalforbidUnknownValues
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 totrue
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
typestack/class-validator (class-validator)
v0.14.0
Compare Source
v0.13.2
Compare Source
Fixed
Array.isArray
in array checks frominstanceof
operatorChanged
libphonenumber-js
package updated to1.9.43
from1.9.7
validator
package updated to13.5.2
from13.5.2
v0.13.1
Compare Source
Added
ArrayUnique
decoratorFixed
IsUUID
decoratorValidationError.toString()
doesn't result in an error whenforbidNonWhitelisted
parameter was usedIsIn
decorator@types/validator
package is correctly installedinlineSources
option is enabled in tsconfig preventing various sourcemap errors when consuming the packageChanged
v0.13.0
Compare Source
Added
always
- allows setting global default foralways
option for decoratorsstrictGroups
- ignore decorators with at least one group, whenValidatorOptions.groups
is emptyConfiguration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.