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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Fix for 25 vulnerabilities #35341

Closed
wants to merge 1 commit into from
Closed

[Snyk] Fix for 25 vulnerabilities #35341

wants to merge 1 commit into from

Conversation

MelvinBot
Copy link

@MelvinBot MelvinBot commented Jan 29, 2024 •
edited by melvin-bot bot
Loading

Details

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
⚠️ Warning 
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 482/1000
Why? Proof of Concept exploit, CVSS 7.5		 Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908		 Yes Proof of Concept
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6057536		 No No Known Exploit
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6062177		 No No Known Exploit
high severity /1000
Why?		 Integer Overflow or Wraparound
SNYK-JS-ELECTRON-6095118		 No Mature
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6095120		 No No Known Exploit
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6095121		 No No Known Exploit
high severity /1000
Why?		 Out-of-Bounds
SNYK-JS-ELECTRON-6095122		 No No Known Exploit
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6100741		 No No Known Exploit
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6105391		 Yes No Known Exploit
high severity /1000
Why?		 Heap-based Buffer Overflow
SNYK-JS-ELECTRON-6137744		 Yes Mature
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6146929		 Yes No Known Exploit
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6146930		 Yes No Known Exploit
high severity /1000
Why?		 Heap-based Buffer Overflow
SNYK-JS-ELECTRON-6146931		 Yes No Known Exploit
high severity /1000
Why?		 Use After Free
SNYK-JS-ELECTRON-6146932		 Yes No Known Exploit
high severity /1000
Why?		 Type Confusion
SNYK-JS-ELECTRON-6173170		 Yes No Known Exploit
high severity /1000
Why?		 Out-of-bounds Write
SNYK-JS-ELECTRON-6173171		 Yes No Known Exploit
high severity /1000
Why?		 Out-of-bounds Read
SNYK-JS-ELECTRON-6179663		 Yes Mature
medium severity 372/1000
Why? Proof of Concept exploit, CVSS 5.3		 Regular Expression Denial of Service (ReDoS)
SNYK-JS-GLOBPARENT-1016905		 Yes Proof of Concept
medium severity /1000
Why?		 Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116		 Yes Proof of Concept
medium severity 265/1000
Why? CVSS 5.3		 Improper Input Validation
SNYK-JS-POSTCSS-5926692		 Yes No Known Exploit
medium severity /1000
Why?		 Cross-site Scripting (XSS)
SNYK-JS-SERIALIZEJAVASCRIPT-6147607		 Yes Proof of Concept
high severity 482/1000
Why? Proof of Concept exploit, CVSS 7.5		 Regular Expression Denial of Service (ReDoS)
SNYK-JS-TRIM-1017038		 Yes Proof of Concept
high severity 375/1000
Why? CVSS 7.5		 Denial of Service (DoS)
SNYK-JS-TRIMNEWLINES-1298042		 Yes No Known Exploit
high severity 375/1000
Why? CVSS 7.5		 Prototype Pollution
SNYK-JS-UNSETVALUE-2400660		 Yes No Known Exploit
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3		 Prototype Pollution
SNYK-JS-XML2JS-5414874		 Yes Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: @storybook/builder-webpack5 The new version differs by 250 commits.

See the full diff

Package name: @storybook/react The new version differs by 250 commits.

See the full diff

Package name: copy-webpack-plugin The new version differs by 29 commits.

See the full diff

Package name: expo The new version differs by 95 commits.

See the full diff

Package name: react-native-blob-util The new version differs by 6 commits.

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@snyk-bot
fix: package.json to reduce vulnerabilities
5af2266 
The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-ANSIREGEX-1583908
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6057536
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6062177
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6095118
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6095120
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6095121
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6095122
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6100741
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6105391
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6137744
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6146929
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6146930
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6146931
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6146932
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6173170
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6173171
- https://snyk.io/vuln/SNYK-JS-ELECTRON-6179663
- https://snyk.io/vuln/SNYK-JS-GLOBPARENT-1016905
- https://snyk.io/vuln/SNYK-JS-INFLIGHT-6095116
- https://snyk.io/vuln/SNYK-JS-POSTCSS-5926692
- https://snyk.io/vuln/SNYK-JS-SERIALIZEJAVASCRIPT-6147607
- https://snyk.io/vuln/SNYK-JS-TRIM-1017038
- https://snyk.io/vuln/SNYK-JS-TRIMNEWLINES-1298042
- https://snyk.io/vuln/SNYK-JS-UNSETVALUE-2400660
- https://snyk.io/vuln/SNYK-JS-XML2JS-5414874
@MelvinBot MelvinBot requested a review from a team as a code owner January 29, 2024 23:40
@melvin-bot melvin-bot bot requested review from tylerkaraszewski and removed request for a team January 29, 2024 23:41
@melvin-bot Melvin Bot
Copy link

melvin-bot bot commented Jan 29, 2024

@tylerkaraszewski Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

pecanoro
pecanoro reviewed Feb 6, 2024
View reviewed changes
package.json
Comment on lines +205 to +207
"@storybook/builder-webpack5": "^7.0.0",
"@storybook/manager-webpack5": "^6.5.10",
"@storybook/react": "^6.5.9",
"@storybook/react": "^7.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was trying to update this in a different PR and this seems to break storybook, just so you are aware

@tylerkaraszewski
Copy link
Contributor

What am I supposed to do with this PR that's created by a bot but has conflicts?

@pecanoro
Copy link
Contributor

pecanoro commented Feb 6, 2024

You can fix the conflicts but you should test that nothing broke after the update, which as I said, it will at least for the storybooks 😄

@tylerkaraszewski
Copy link
Contributor

Heh, well then what? Don't merge it?

@pecanoro
Copy link
Contributor

Ideally, you should figure out how to fix it and why storybooks break after updating, but if you don't want to do it, I am not sure, just close the PR? 😄

@pecanoro pecanoro closed this Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@pecanoro pecanoro pecanoro left review comments

@tylerkaraszewski tylerkaraszewski Awaiting requested review from tylerkaraszewski

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@MelvinBot @tylerkaraszewski @pecanoro @snyk-bot