nodejs-bl: buffer over-read vulnerability leads to corrupted BufferList which can result in uninitialized memory being leaked
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | bl | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2698-1 | node-bl security update |
EUVD |
EUVD-2020-1218 | 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. |
Github GHSA |
GHSA-pp7h-53gx-mx7r | Remote Memory Exposure in bl |
Ubuntu USN |
USN-5098-1 | bl vulnerability |
Ubuntu USN |
USN-5159-1 | bl vulnerability |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.1% (2.097% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.