Insertion of Sensitive Information into Externally-Accessible File or Directory in storybook

Summary

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability in versions from 7.x prior to 7.6.21, 8.x prior to 8.6.15, 9.x prior to 9.1.17, and 10.x prior to 10.1.10 relates to Storybooks handling of environment variables defined in a ".env" file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the "storybook build" command. When a built Storybook is published to the web, the bundles source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run "storybook build" directly or indirectly) in a directory that contains a ".env" file (including variants like ".env.local") and publish the built Storybook to the web. Storybooks built without a ".env" file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than ".env" files. Storybook runtime environments (i.e. "storybook dev") are not affected. Deployed applications that share a repo with your Storybook are not affected. Maintainers additionally recommend that users audit for any sensitive secrets provided via ".env" files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with "STORYBOOK_" or use the "env" property in Storybooks configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.