ee-cdn-cli no longer passes your deploy token to the packaging tool
TL;DR: From ee-cdn-cli 0.4.1, the packaging tool the CLI downloads starts with only what it needs to run, so your deploy token and other credentials aren't passed to it. Deploy to Evolving Edge CDN v1.0.1 runs 0.4.1.
To package your site, ee-cdn-cli downloads and runs a separate tool, ee-builder. Until now, the CLI started it with everything in its own environment, including your deploy token in EE_CDN_TOKEN and any other credentials your CI job had. ee-builder never needed any of them, because the CLI does the upload itself.
From 0.4.1, ee-builder is started with only the basic system settings it needs to run: the path, home and temp folders, locale, and on Windows the system variables. Your deploy token and other credentials, including ones whose names don’t look like credentials, are no longer passed to it.
No incident of this has occurred. This is a proactive security fix.
Limits
- This guards against accidental exposure, such as a packaging tool that logs or reports its environment.
- It doesn’t stop a hostile packaging tool. ee-builder runs as the same user as the CLI, so a tampered copy could still reach your token by other means. To control exactly which ee-builder runs in CI, pin
--builder-version(builder-versionin the Action) and commit.ee-builder-lock.json.
What you need to do
- If you run
ee-cdn-cliyourself, update to 0.4.1 or later. - If you use the Deploy to Evolving Edge CDN Action at
@v1, you already have it: v1.0.1 runsee-cdn-cli0.4.1. - If you’ve pinned the Action to
@v1.0.0, change it to@v1.0.1.