shakapacker
Affected
- introduced
0, fixed9.5.0(semver)
Fixed versions
9.5.0
Fix
- Fixed version
9.5.0npm install [email protected]
Advisory
Also known as: None
Shakapacker has environment variable leak via EnvironmentPlugin that exposes secrets to client-side bundles
Summary
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.VARIABLE_NAME.
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:
DATABASE_URL - Database credentialsAWS_SECRET_ACCESS_KEY - AWS credentials RAILS_MASTER_KEY - Rails encrypted credentials keySTRIPE_SECRET_KEY, TWILIO_AUTH_TOKEN - Third-party API keysSeverity: Critical - secrets are exposed in publicly accessible JavaScript files.
Root Cause
The original code used:
new webpack.EnvironmentPlugin(process.env)
This makes every environment variable available for substitution. If any code references process.env.SECRET_KEY, that value is embedded in the bundle.
Patches
Upgrade to version 9.5.0 or later, which uses an allowlist approach that only exposes NODE_ENV, RAILS_ENV, and WEBPACK_SERVE by default.
Workarounds
If developers cannot upgrade immediately:
process.env.X references to sensitive variablesMigration
After upgrading, if client-side code needs access to specific environment variables:
Option 1: Use the `SHAKAPACKER_PUBLIC_` prefix (recommended)
# Variables with this prefix are automatically exposed
export SHAKAPACKER_PUBLIC_API_URL="https://api.example.com"
Option 2: Use `SHAKAPACKER_ENV_VARS`
SHAKAPACKER_ENV_VARS=API_URL,FEATURE_FLAG bundle exec rails assets:precompile
Action Required
After upgrading, rotate any secrets that may have been exposed in previously compiled JavaScript bundles.
Resources
High Basis: The source's own band: HIGH
0, fixed 9.5.0 (semver)9.5.0
9.5.0npm install [email protected]0, fixed 9.5.0 (ecosystem)9.5.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0