1 # disallow use of the Buffer() constructor (no-buffer-constructor)
3 In Node.js, the behavior of the `Buffer` constructor is different depending on the type of its argument. Passing an argument from user input to `Buffer()` without validating its type can lead to security vulnerabilities such as remote memory disclosure and denial of service. As a result, the `Buffer` constructor has been deprecated and should not be used. Use the producer methods `Buffer.from`, `Buffer.alloc`, and `Buffer.allocUnsafe` instead.
7 This rule disallows calling and constructing the `Buffer()` constructor.
9 Examples of **incorrect** code for this rule:
13 new Buffer([1, 2, 3]);
18 new Buffer(res.body.amount);
19 new Buffer(res.body.values);
22 Examples of **correct** code for this rule:
26 Buffer.allocUnsafe(5);
27 Buffer.from([1, 2, 3]);
29 Buffer.alloc(res.body.amount);
30 Buffer.from(res.body.values);
35 If you don't use Node.js, or you still need to support versions of Node.js that lack methods like `Buffer.from`, then you should not enable this rule.
39 * [Buffer API documentation](https://nodejs.org/api/buffer.html)
40 * [Let's fix Node.js Buffer API](https://github.com/ChALkeR/notes/blob/master/Lets-fix-Buffer-API.md)
41 * [Buffer(number) is unsafe](https://github.com/nodejs/node/issues/4660)