Remote Memory Exposure in bl
bl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| bl npm |
|
|
bl
| Product | Affected | Fixed in |
|---|---|---|
| bl npm |
|
|
A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.
From the CVE record · hackerone
A buffer over-read in bl can corrupt BufferList state when attacker-supplied input reaches consume() and becomes negative. Subsequent .slice() calls can expose uninitialized memory. The input does not specify whether exploitation requires network access, authentication, or further user interaction.
Check applications using npm bl versions below 1.2.3, 2.0.0 through 2.2.0, 3.0.0, or 4.0.0 through 4.0.2.