Vulnerability Database · npm · bl · Version
bl 0.2.0
0.2.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 23 Jul 2013
Licence MIT
Also known from other sources 2
Newer releases 89
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
bl 0.2.0 vulnerabilities
2 vulnerabilities cover bl 0.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2020-8244: Remote Memory Exposure in bl | 6.5 medium | 1.2.3 | 02 Sep 2020 |
| Memory Exposure Vulnerability in bl | N/A medium | 0.9.5 | 03 Jun 2019 |
Looking for another version, or everything Vulert holds for bl?
Questions
About bl 0.2.0
Is bl 0.2.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover bl 0.2.0: 0 critical, 0 high, 2 medium and 0 low. Each entry above names the fixed version to move to.
Is 0.2.0 the latest release of bl?
No. 0.2.0 was published 23 Jul 2013, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor bl for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the bl version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.