Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

shakapacker

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

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

  1. High, CVSS 7.5npmAmendedPublished

    Shakapacker has environment variable leak via EnvironmentPlugin that exposes secrets to client-side bundles

    GHSA-96qw-h329-v5rg

    Affected
    • npm shakapacker < 9.5.0
    Fixed in
    9.5.0· Vendor fix available
    Issue
    Since 2017, the default webpack plugins have passed the entire process.env to EnvironmentPlugin. This pattern exposed ALL build environment variables to client-side JavaScript bundles whenever application code (or any dependency) referenced process.env.VARIABLENAME. This is not a regression - the vulnerable code has existed since the original Webpacker implementation. No recent code change in Shakapacker triggered this issue. Impact Any environment variable in the build environment that is referenced in client-side code (including third-party dependencies) is embedded directly into the JavaScript bundle. This includes: - DATABASEURL - Database credentials - AWSSECRETACCESSKEY - AWS credentials - RAILSMASTERKEY - Rails encrypted credentials key - STRIPESECRETKEY, TWILIOAUTHTOKEN - Third-party API keys - Any other secrets present in the build environment Severity: Critical - secrets are exposed in publicly accessible JavaScript files. Root Cause The original code used: This…

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