Skip to content

← Public intelligence

crates.io package

pleaser

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. High, CVSS 7.8crates.ioPublished

    Permissions bypass in pleaser

    CVE-2021-31155 · GHSA-vc5p-j8vw-mc6x

    Affected
    • crates.io pleaser < 0.4.0
    Fixed in
    0.4.0· Vendor fix available
    Issue
    Failure to normalize the umask in pleaser before 0.4.0 allows a local attacker to gain full root privileges if they are allowed to execute at least one command.

    Recommended action: Upgrade to 0.4.0 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.8crates.ioPublished

    Permissions bypass in pleaser

    CVE-2021-31154 · GHSA-pp74-39w2-v4w9

    Affected
    • crates.io pleaser < 0.4.0
    Fixed in
    0.4.0· Vendor fix available
    Issue
    pleaseedit in pleaser before 0.4.0 uses predictable temporary filenames in /tmp and the target directory. This allows a local attacker to gain full root privileges by staging a symlink attack.

    Recommended action: Upgrade to 0.4.0 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. Low, CVSS 3.3crates.ioPublished

    File exposure in pleaser

    CVE-2021-31153 · GHSA-f3fg-5j9p-vchc

    Affected
    • crates.io pleaser < 0.4.0
    Fixed in
    0.4.0· Vendor fix available
    Issue
    pleaser before 0.4.0 allows a local unprivileged attacker to gain knowledge about the existence of files or directories in privileged locations via the searchpath function, the --check option, or the -d option.

    Recommended action: Upgrade to 0.4.0 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 →