Dependency vulnerability: qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion

[SimonLandeholm]

Sails version: 1.5.3

qs <6.14.1
Severity: high
qs's arrayLimit bypass in its bracket notation allows DoS via memory exhaustion - GHSA-6rw7-vpxm-498p
fix available via npm audit fix --force
Will install sails@0.12.14, which is a breaking change
node_modules/qs
node_modules/waterline-utils/node_modules/qs
body-parser <=1.20.3 || 2.0.0-beta.1 - 2.0.2
Depends on vulnerable versions of qs
node_modules/body-parser
express 2.5.8 - 2.5.11 || 3.2.1 - 3.2.3 || 4.0.0-rc1 - 4.21.2 || 5.0.0-alpha.1 - 5.0.1
Depends on vulnerable versions of body-parser
Depends on vulnerable versions of qs
node_modules/express
sails <=0.8.895 || >=0.12.4-rc1
Depends on vulnerable versions of express
Depends on vulnerable versions of skipper
node_modules/sails
skipper >=0.6.0
Depends on vulnerable versions of body-parser
node_modules/skipper
waterline-utils >=1.4.1
Depends on vulnerable versions of qs
node_modules/waterline-utils

[sailsbot]

@SimonLandeholm Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.

[SimonLandeholm]

💀 🕸️

[eashaw]

Hey @SimonLandeholm, Thanks for creating this issue. We released Sails v1.5.16 and Skipper v0.9.6 with upgraded versions of Express and body-parser.