Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Security] Vulnerability of Low severity in "@storybook/addon-info > marksy > marked" #7842

Closed
Bazze opened this issue Aug 22, 2019 · 14 comments

Comments

@Bazze
Copy link

Bazze commented Aug 22, 2019

Describe the bug
New vulnerability discovered in July in a sub dependency: @storybook/addon-info > marksy > marked

This is in version 5.1.11 of @storybook/addon-info.

https://www.npmjs.com/advisories/1076

Screenshots
Screenshot 2019-08-22 at 14 29 24

System

Environment Info:
  npmPackages:
    @storybook/addon-actions: ^5.1.11 => 5.1.11
    @storybook/addon-backgrounds: ^5.1.11 => 5.1.11
    @storybook/addon-info: ^5.1.11 => 5.1.11
    @storybook/addon-knobs: ^5.1.11 => 5.1.11
    @storybook/addon-links: ^5.1.11 => 5.1.11
    @storybook/addon-viewport: ^5.1.11 => 5.1.11
    @storybook/react: ^5.1.11 => 5.1.11
@shilman
Copy link
Member

shilman commented Aug 22, 2019

Addon-info is being superceded by addon-docs, which fixes a bunch of bugs and is easier to maintain. Please give it a try! https://medium.com/storybookjs/storybook-docspage-e185bc3622bf

@ZebraFlesh
Copy link

Pointing to a beta release is not really an appropriate resolution for a security issue. Can we just get an updated 5.1.x release with remediated dependencies?

@shilman
Copy link
Member

shilman commented Aug 31, 2019

@ZebraFlesh PRs welcome

@ZebraFlesh
Copy link

ZebraFlesh commented Sep 1, 2019

I dug into this a bit and found the following:

  • upgrading storybook's marksy dependency on marked generates some test failures
  • using the marked demo, the same test input generates good output (example)

This leads me to believe that the renderers that marksy supplies to marked are bad, but I lack project familiarity to determine what the problem is.

@stale
Copy link

stale bot commented Sep 22, 2019

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Sep 22, 2019
@reanimatedmanx
Copy link

Heyo, this is still present in @storybook/addon-info": "~5.2.1 can we get just fix related to that regexp DoS issue. I know there is a proposal to just move to addon-docs but at the project I am working on, there is a sceptical approach to new libraries (yeah I know how it sounds). So just rising this issue once again as I saw it already being marked as innactive

@stale stale bot removed the inactive label Oct 4, 2019
@stale
Copy link

stale bot commented Oct 25, 2019

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Oct 25, 2019
@1Jesper1
Copy link

Fix please

@stale stale bot removed the inactive label Nov 11, 2019
@shilman
Copy link
Member

shilman commented Nov 11, 2019

If anybody wants to issue a PR for a fix, I'm happy to get it merged. In the meantime, addon-docs has been released for two months and is getting better every day. Here's a good example of a production system using it:

https://reaviz.io/?path=/story/docs-intro--page

@stale
Copy link

stale bot commented Dec 2, 2019

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

@stale stale bot added the inactive label Dec 2, 2019
@fralewsmi
Copy link

Related: storybookjs/marksy#78

@shilman
Copy link
Member

shilman commented Dec 26, 2019

Jiminy cricket!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.3.0-rc.3 containing PR #9234 that references this issue. Upgrade today to try it out!

You can find this prerelease on the @next NPM tag.

Closing this issue. Please re-open if you think there's still more to do.

@shilman shilman closed this as completed Dec 26, 2019
@imgyf
Copy link

imgyf commented Jun 10, 2020

Hi @shilman, I'm facing the same issue in npm audit. This is in version ^5.3.18 of @storybook/addon-info.

┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Moderate      │ Regular Expression Denial of Service                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ marked                                                       │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ >=0.6.2                                                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ @storybook/addon-info [dev]                                  │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ @storybook/addon-info > marksy > marked                      │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/812                             │
└───────────────┴──────────────────────────────────────────────────────────────┘

@shilman
Copy link
Member

shilman commented Jun 11, 2020

@gohyifan #7842 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants