NestJS developers will find a subtle yet potentially crucial update in @nestjs/common version 4.5.5 compared to its predecessor, 4.5.4. Both versions share the same core dependencies including "cli-color":"1.1.0", "class-validator":"0.7.3", and "class-transformer":"0.1.8", indicating a consistent set of tools for command-line coloring, data validation, and object transformation, respectively. They also maintain the same peer dependency on "reflect-metadata":"0.1.10", ensuring compatibility with reflection capabilities required by NestJS. The MIT license and author information remain unchanged, signifying ongoing support under the same open-source terms and maintainer.
The primary difference lies in the release date. Version 4.5.5 was published on January 2nd, 2018, while version 4.5.4 was released on December 30th, 2017. This 3-day gap suggests that version 4.5.5 likely incorporates bug fixes, minor improvements, or dependency updates that address any issues discovered in the preceding version. While the specifics of these changes aren't detailed in the provided data, developers are advised to consult the official NestJS changelog or release notes for a comprehensive understanding of the enhancements. Upgrading to 4.5.5 is recommended to leverage these potential refinements and ensure optimal stability and performance within their NestJS applications. The tarball URLs point to the respective package distributions on npm, facilitating easy installation.
All the vulnerabilities related to the version 4.5.5 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.
