Skip to content

← Public intelligence

npm package

bl

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5npmAmendedPublished

    Remote Memory Exposure in bl

    CVE-2020-8244 · GHSA-pp7h-53gx-mx7r

    Affected
    • npm bl >= 3.0.0, <= 3.0.0; >= 4.0.0, < 4.0.3; < 1.2.3; >= 2.0.0, < 2.2.1
    Fixed in
    1.2.33.0.14.0.32.2.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 4.0.3, 3.0.1, 2.2.1 or 1.2.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. UnratednpmAmendedPublished

    Memory Exposure in bl

    GHSA-wrw9-m778-g6mc

    Affected
    • npm bl < 0.9.5; >= 1.0.0, <= 1.0.0
    Fixed in
    0.9.51.0.1· Vendor fix available
    Issue
    Versions of bl before 0.9.5 and 1.0.1 are vulnerable to memory exposure. bl.append(number) in the affected bl versions passes a number to Buffer constructor, appending a chunk of uninitialized memory Recommendation Update to version 0.9.5, 1.0.1 or later.

    Recommended action: Upgrade to 1.0.1 or 0.9.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →