Version 4.5.14 of the @nestjs/common package is a minor update over the previous stable release, 4.5.13. Both versions share the same core dependencies including cli-color for command-line styling, class-validator for data validation, and class-transformer for object transformation. They also declare the same peer dependency on reflect-metadata. The package description remains consistent, highlighting Nest as a modern, fast, and powerful Node.js web framework. The author and license (MIT) are unchanged between the two releases.
Essentially, the difference between the two versions comes down to the release date, as version 4.5.14 was published roughly 20 minutes after 4.5.13. The fileCount and unpackedSize properties in the dist object are identical. For developers already using NestJS, upgrading from 4.5.13 to 4.5.14 likely introduces no significant behavioral changes if the metadata reflects the real changes in the package and only includes bug fixes, performance improvements, or very minor adjustments that don't impact existing API usage. It's always recommended to review the changelog for any included changes before updating, although it isn't provided in the data.
All the vulnerabilities related to the version 4.5.14 of the package
nest allows a remote attacker to execute arbitrary code via the Content-Type header
File Upload vulnerability in nestjs nest prior to v.11.0.16 allows a remote attacker to execute arbitrary code via the Content-Type header.
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.
Inefficient Regular Expression Complexity in validator.js
validator.js prior to 13.7.0 is vulnerable to Inefficient Regular Expression Complexity
Prototype pollution in class-transformer
class-transformer through 0.2.3 is vulnerable to Prototype Pollution. The 'classToPlainFromExist' function could be tricked into adding or modifying properties of 'Object.prototype' using a 'proto' payload.
