Skip to content

← Public intelligence

npm package

aegir

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. Critical, CVSS 9.6npmAmendedPublished

    Exposure of Sensitive Information to an Unauthorized Actor in AEgir

    CVE-2020-11059 · GHSA-qfcv-5whw-7pcw

    Affected
    • npm aegir >= 21.7.0, < 21.10.1
    Fixed in
    21.10.1· Vendor fix available
    Issue
    Impact aegir publish and aegir build may leak secrets from environmental variables in the browser bundle published to npm. Patches The code has been patched, users should upgrade to = 21.10.1 Workarounds Run printenv to check your environment variables and revoke any secrets. For more information If you have any questions or comments about this advisory: Open an issue in aegir

    Recommended action: Upgrade to 21.10.1 or later, 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

    Github Token Leak in aegir

    CVE-2017-16225 · GHSA-6xhf-x49c-m5m6

    Affected
    • npm aegir >= 12.0.0, <= 12.0.7
    Fixed in
    12.0.8· Vendor fix available
    Issue
    Affected versions of aegir bundle and publish the current users github token to npm when aegir-release is executed. Recommendation Update to version 12.0.8 or later. If you used this module to do a release for your project you should invalidate the GitHub tokens that were leaked.

    Recommended action: Upgrade to 12.0.8 or later, 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 →