GHSA-96h4-vgxj-gvm2: Nest: Unbounded memory growth in the NestJS TCP microservice transport
A peer that can open a TCP connection to a NestJS microservice using the built-in TCP transport can make the server process allocate memory without limit, on either side of the connection, until the process is killed by the OS or by its container memory limit. No authentication, no credentials, and no valid message are required.
Applications are affected only if they start a microservice with Transport.TCP and the
transport’s port is reachable by an untrusted peer.
References
- github.com/advisories/GHSA-96h4-vgxj-gvm2
- github.com/nestjs/nest/commit/6ca2dd894a6ff964d318724f363061652e822920
- github.com/nestjs/nest/commit/781843ac98d429fe1d541c52c7126850be5989a7
- github.com/nestjs/nest/commit/dee4ed4dbc2e18e1e722619927647f5441dfe812
- github.com/nestjs/nest/pull/17746
- github.com/nestjs/nest/pull/17749
- github.com/nestjs/nest/releases/tag/v11.2.5
- github.com/nestjs/nest/releases/tag/v12.0.3
- github.com/nestjs/nest/security/advisories/GHSA-96h4-vgxj-gvm2
Code Behaviors & Features
Detect and mitigate GHSA-96h4-vgxj-gvm2 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →