Сковорода Никита Андреевич

**Name of the Vulnerable Software and Affected Versions** Node.js versions prior to 10.9.0 **Description** The issue is related to an argument processing flaw in the `Buffer.alloc()` method. This method is intended to return initialized memory, but due to the flaw, it can return uninitialized memory. The third argument, `encoding`, can be misinterpreted as the `start` to a fill operation if passed as a number. This may lead to the return of uncleared memory blocks that may contain sensitive information, particularly when `Buffer.alloc()` arguments are derived from user input. **Recommendations** For Node.js versions prior to 10.9.0, update to version 10.9.0 or later to resolve the issue. As a temporary workaround, consider validating and sanitizing user input before passing it to the `Buffer.alloc()` method to minimize the risk of exploitation. Restrict access to sensitive information and avoid using the `encoding` argument as a number to prevent misinterpretation by the internal "fill" method.

**Name of the Vulnerable Software and Affected Versions** Node.js versions prior to 6.14.4 Node.js versions prior to 8.11.4 Node.js versions prior to 10.9.0 **Description** The issue arises when Node.js is used with UCS-2 encoding, which is recognized under the names `ucs2`, `ucs-2`, `utf16le`, and `utf-16le`. In this context, the `Buffer#write()` function can be exploited to write beyond the boundaries of a single buffer. Specifically, writes that initiate from the second-to-last position of a buffer lead to a miscalculation of the maximum length of the input bytes to be written. **Recommendations** For versions prior to 6.14.4, update to version 6.14.4 or later. For versions prior to 8.11.4, update to version 8.11.4 or later. For versions prior to 10.9.0, update to version 10.9.0 or later.

**Name of the Vulnerable Software and Affected Versions** Node.js versions (affected versions not specified) **Description** The HTTP parser in Node.js ignores spaces in the `Content-Length` header, allowing input such as `Content-Length: 1 2` to be interpreted as having a value of `12`. This does not align with the HTTP specification, which does not allow for spaces in the `Content-Length` value. The security risk of this flaw is considered to be very low, as it is difficult to craft an attack that makes use of this flaw in a way that could not already be achieved by supplying an incorrect value for `Content-Length`. However, vulnerabilities may exist in user-code that make incorrect assumptions about the potential accuracy of this value compared to the actual length of the data supplied. **Recommendations** For all affected versions, users crafting lower-level HTTP utilities are advised to re-check the length of any input supplied after parsing is complete. At the moment, there is no information about a newer version that contains a fix for this vulnerability.