Skip to content

← Public intelligence

crates.io package

fltk

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

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

  1. Critical, CVSS 9.1crates.ioPublished

    Out of bounds read in fltk

    CVE-2021-28308 · GHSA-vjmg-pc8h-p6p8

    Affected
    • crates.io fltk < 0.15.3
    Fixed in
    0.15.3· Vendor fix available
    Issue
    An issue was discovered in the fltk crate before 0.15.3 for Rust. There is an out-of bounds read because the pixmap constructor lacks pixmap input validation.

    Recommended action: Upgrade to 0.15.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5crates.ioPublished

    Null pointer deference in fltk

    CVE-2021-28306 · GHSA-5pg8-h4gv-m3p8

    Affected
    • crates.io fltk < 0.15.3
    Fixed in
    0.15.3· Vendor fix available
    Issue
    An issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a multi label type if the image is nonexistent.

    Recommended action: Upgrade to 0.15.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. High, CVSS 7.5crates.ioPublished

    Null pointer deference in fltk

    CVE-2021-28307 · GHSA-7qcc-g2m9-8533

    Affected
    • crates.io fltk < 0.15.3
    Fixed in
    0.15.3· Vendor fix available
    Issue
    An issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a non-raster image for a window icon.

    Recommended action: Upgrade to 0.15.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →