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

fix: security upgrade follow-redirects from 1.13.0 to 1.14.7 #7773

Closed

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

merge advice

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 658/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.3
Information Exposure
SNYK-JS-FOLLOWREDIRECTS-2332181
No Proof of Concept

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

Commit messages
Package name: follow-redirects The new version differs by 40 commits.

See the full diff

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


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Security upgrade follow-redirects from 1.13.0 to 1.14.7 refactor: security upgrade follow-redirects from 1.13.0 to 1.14.7 Jan 13, 2022
@codecov
Copy link

codecov bot commented Jan 13, 2022

Codecov Report

❗ No coverage uploaded for pull request base (release-4.x.x@65c13fe). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@               Coverage Diff                @@
##             release-4.x.x    #7773   +/-   ##
================================================
  Coverage                 ?   84.11%           
================================================
  Files                    ?      169           
  Lines                    ?    12442           
  Branches                 ?        0           
================================================
  Hits                     ?    10465           
  Misses                   ?     1977           
  Partials                 ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65c13fe...2286e44. Read the comment docs.

@mtrezza mtrezza changed the title refactor: security upgrade follow-redirects from 1.13.0 to 1.14.7 fix: security upgrade follow-redirects from 1.13.0 to 1.14.7 Jan 13, 2022
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

Copy link
Member

@mtrezza mtrezza left a comment

Choose a reason for hiding this comment

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

Before merging this, auto release needs to be configured for the 4.x LTS branch, so that a release is triggered.

@phillycheeze
Copy link

Are there plans to push a new release to the 4.x branch with the fix?

@mtrezza
Copy link
Member

mtrezza commented Feb 6, 2022

We are currently focused on Parse Server v5 release, which will also include this fix.

@mtrezza
Copy link
Member

mtrezza commented Feb 12, 2022

Auto-release has been added to the 4.x LTS branch, so this can be merged if tests pass.

@mtrezza
Copy link
Member

mtrezza commented Feb 12, 2022

Closing in favor of #7803.

@mtrezza mtrezza closed this Feb 12, 2022
@mtrezza mtrezza deleted the snyk-fix-ca454dc3d8d145ff176b5ff86ffb6bde branch February 12, 2022 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants