Uninitialized Memory Exposure Affecting base64-url package, versions <2.0.0
Threat Intelligence
Snyk has a published code exploit for this vulnerability.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDnpm:base64-url:20180512
- published13 May 2018
- disclosed12 May 2018
- creditChALkeR
Introduced: 12 May 2018
CVE NOT AVAILABLE CWE-201 (opens in a new tab)How to fix?
Upgrade base64-url to version 2.0.0 or higher.
Note This is vulnerable only for Node <=4
Overview
base64-url Base64 encode, decode, escape and unescape for URL applications.
Affected versions of this package are vulnerable to Uninitialized Memory Exposure. An attacker may extract sensitive data from uninitialized memory or may cause a DoS by passing in a large number, in setups where typed user input can be passed (e.g. from JSON).
Details
The Buffer class on Node.js is a mutable array of binary data, and can be initialized with a string, array or number.
const buf1 = new Buffer([1,2,3]);
// creates a buffer containing [01, 02, 03]
const buf2 = new Buffer('test');
// creates a buffer containing ASCII bytes [74, 65, 73, 74]
const buf3 = new Buffer(10);
// creates a buffer of length 10
The first two variants simply create a binary representation of the value it received. The last one, however, pre-allocates a buffer of the specified size, making it a useful buffer, especially when reading data from a stream.
When using the number constructor of Buffer, it will allocate the memory, but will not fill it with zeros. Instead, the allocated buffer will hold whatever was in memory at the time. If the buffer is not zeroed by using buf.fill(0), it may leak sensitive information like keys, source code, and system info.