[Snyk] Security upgrade express from 4.16.3 to 4.22.0

[jhamot]

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

Snyk changed the following file(s):

• script/update-server/package.json
• script/update-server/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

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

---

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

[jhamot]

This is a minor version upgrade within the Express 4.x series, but it includes several behavioral changes and one notable accidental breaking change in the target version 4.22.0 that require attention.

Key Changes:

• Accidental Breaking Change in 4.22.0: This version included an unintentional breaking change related to the extended query parser (qs). This change was reverted in version 4.22.1 because it was erroneous. Applications relying on the previous query parsing behavior may be affected.
• Stricter Validation: Starting with version 4.18.0, the res.cookie() method now rejects invalid Date objects provided as the expires option, which could surface issues in existing code that was passing invalid data.
• Security Fixes: The upgrade includes numerous security patches across versions 4.17.3 to 4.21.2, addressing vulnerabilities in dependencies and Express itself, such as open redirects and XSS.

Recommendation: Due to the accidental breaking change in 4.22.0, it is strongly recommended to upgrade to express@4.22.1 or higher to avoid the query parser issue. If you must use 4.22.0, thoroughly test application functionality that relies on parsing query strings.

Source: Express.js 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.