storybook@10.1.6 vulnerabilities

Storybook: Develop, document, and test UI components in isolation

  • latest version

    10.2.15

  • latest non vulnerable version

  • first published

    9 years ago

  • latest version published

    23 hours ago

  • licenses detected

    • >=0.0.0-pr-22236-sha-107ce09c <0.0.0; >=0.2.0
  • Direct Vulnerabilities

    Known vulnerabilities in the storybook package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Arbitrary Code Injection

    storybook is a frontend workshop for building UI components and pages in isolation.

    Affected versions of this package are vulnerable to Arbitrary Code Injection via the WebSocket message handlers for creating and saving stories, specifically through unsanitized input in the componentFilePath field. An attacker can achieve persistent code execution or inject malicious scripts by sending crafted WebSocket messages to the local development server.

    Note:

    This is only exploitable if a developer visits a malicious website while their local development server is running, or if the development server is intentionally exposed publicly.

    How to fix Arbitrary Code Injection?

    Upgrade storybook to version 7.6.23, 8.6.17, 9.1.19, 10.2.10 or higher.

    <7.6.23>=8.0.0-alpha.0 <8.6.17>=9.0.0-alpha.0 <9.1.19>=10.0.0-beta.0 <10.2.10
    • L
    Insertion of Sensitive Information into Externally-Accessible File or Directory

    storybook is a frontend workshop for building UI components and pages in isolation.

    Affected versions of this package are vulnerable to Insertion of Sensitive Information into Externally-Accessible File or Directory via the storybook build command. An attacker can access sensitive environment variables by viewing the bundled source code after the build artifacts are published to the web. This is only exploitable if the build is performed in a directory containing a .env file and the resulting build is published to the web.

    How to fix Insertion of Sensitive Information into Externally-Accessible File or Directory?

    Upgrade storybook to version 7.6.21, 8.6.15, 9.1.17, 10.1.10, 10.2.0-alpha.7 or higher.

    >=7.0.0 <7.6.21>=8.0.0-alpha.0 <8.6.15>=9.0.0-alpha.0 <9.1.17>=10.0.0-beta.0 <10.1.10>=10.2.0-alpha.0 <10.2.0-alpha.7