Skip to content
This repository was archived by the owner on Mar 17, 2025. It is now read-only.

Conversation

@depfu
Copy link

@depfu depfu bot commented Jul 27, 2023


🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sails (0.12.14 → 1.5.7) · Repo · Changelog

Security Advisories 🚨

🚨 DoS vulnerability for apps with sockets enabled

Impact

In Sails apps <=v1.5.6, an attacker can send a virtual request that will cause the node process to crash.

Patches

This behavior was fixed in Sails v1.5.7

Workarounds

Disable the sockets hook and remove the sails.io.js client

References

#7287

Big thanks to @ThomasRinsma at Codean!

Release Notes

1.5.7

What's Changed

Big thanks to @ThomasRinsma at Codean!

Full Changelog: v1.5.5...v1.5.7

1.4.0

  • Support sameSite:none in cookie options (thanks @pixnlove!)

1.3.1

  • Updated the machine-as-action dependency to include a reminder about escaping strings with dynamic data when they're injected (Thanks @dusterherz for letting us know about this)

1.2.5

  • Added more info to the error message shown when an app fails to lift
  • Updated the sails-generate dependency

1.2.2

• Update merge-defaults dependency to resolve potential vulnerabilities
• Update sails-stringfile dependency to resolve potential vulnerabilities
• Update sort-route-addresses dependency to resolve potential vulnerabilities

1.2.1

  • Added sails migrate for quickly running auto-migrations by hand
  • The output of sails inspect no longer includes controller information
  • When loading user hooks, if sails.config.loadHooks is specified, skip hooks whose names aren't explicitly included
  • Increased time to display warning message in config/bootstrap.js from 5 seconds to 30 seconds
  • Switched to using updateOne in the "update" blueprint
  • Blueprint queries no longer include fetch: true by default, to avoid warnings from updateOne
  • Update error mesage in default serverError response to use flaverr
  • In lib/router/res.js, instead of always setting 'content-type' to 'application/json', only set it if res.get('content-type') is falsy
  • Update flaverr dependency
  • Update i18n-2 dependency to resolve deprecation warning
  • Update rc dependency to address potential vulnerabilities
  • Update machinepack-process dependency to address potential vulnerabilities
  • Update machinepack-redis dependency to address potential vulnerabilities

1.2.0 (from changelog)

  • Added sails migrate for quickly running auto-migrations by hand
  • The output of sails inspect no longer includes controller information
  • When loading user hooks, if sails.config.loadHooks is specified, skip hooks whose names aren't explicitly included
  • Increased time to display warning message in config/bootstrap.js from 5 seconds to 30 seconds
  • Switched to using updateOne in the "update" blueprint
  • Blueprint queries no longer include fetch: true by default, to avoid warnings from updateOne
  • Update error mesage in default serverError response to use flaverr
  • In lib/router/res.js, instead of always setting 'content-type' to 'application/json', only set it if res.get('content-type') is falsy
  • Update flaverr dependency
  • Update i18n-2 dependency to resolve deprecation warning
  • Update rc dependency to address potential vulnerabilities
  • Update machinepack-process dependency to address potential vulnerabilities
  • Update machinepack-redis dependency to address potential vulnerabilities

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Jul 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant