[Snyk] Security upgrade express from 4.18.2 to 4.22.0

[mrb0unce]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-15268416	708

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[mrb0unce]

This is a minor version upgrade for Express from 4.18.2 to 4.22.0. While minor versions are typically non-breaking, this update contains a behavioral change that warrants a medium risk assessment.

Key Changes:

• Query Parser Behavior: Version 4.22.0 includes a fix for the extended query parser. The req.query object is now created as a plain object (Object.create(null)), so it no longer inherits properties from Object.prototype. This was a correctness fix to prevent potential prototype pollution issues.
• Security Fixes: The releases between 4.18.2 and 4.22.0 include patches for security vulnerabilities, notably an open redirect vulnerability fixed in version 4.19.0.

Potential Impact:
The change to the query parser is the primary risk. If your application code uses the extended query parser (the default in Express 4) and relies on Object.prototype methods or properties being available on the req.query object (e.g., req.query.hasOwnProperty(...)), it will break. This is considered an edge case, but requires verification.

Recommendation:
Verify that any code interacting with req.query does not depend on inherited Object prototype properties. Test query parameter handling thoroughly after the upgrade.

Source: Express 4.x Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.