[Snyk] Security upgrade express from 4.18.2 to 4.21.1

[schalla0791]

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

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
	601/1000 Why? Recently disclosed, Has a fix available, CVSS 6.3	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	No	No Known Exploit

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

Commit messages

Package name: express

The new version differs by 112 commits.

• 8e229f9 4.21.1
• a024c8a fix(deps): cookie@0.7.1
• 7e562c6 4.21.0
• 1bcde96 fix(deps): qs@6.13.0 (#5946)
• 7d36477 fix(deps): serve-static@1.16.2 (#5951)
• 40d2d8f fix(deps): finalhandler@1.3.1
• 77ada90 Deprecate `"back"` magic string in redirects (#5935)
• 21df421 4.20.0
• 4c9ddc1 feat: upgrade to serve-static@0.16.0
• 9ebe5d5 feat: upgrade to send@0.19.0 (#5928)
• ec4a01b feat: upgrade to body-parser@1.20.3 (#5926)
• 54271f6 fix: don't render redirect values in anchor href
• 125bb74 path-to-regexp@0.1.10 (#5902)
• 2a980ad merge-descriptors@1.0.3 (#5781)
• a3e7e05 docs: specify new instructions for `question` and `discuss`
• c5addb9 deps: path-to-regexp@0.1.8 (#5603)
• e35380a docs: add @ IamLizu to the triage team (#5836)
• f5b6e67 docs: update scorecard link (#5814)
• 2177f67 docs: add OSSF Scorecard badge (#5436)
• f4bd86e Replace Appveyor windows testing with GHA (#5599)
• 2ec589c Fix Contributor Covenant link definition reference in attribution section (#5762)
• 4cf7eed remove minor version pinning from ci (#5722)
• 6d08471 📝 update people, add ctcpip to TC (#5683)
• 61421a8 skip QUERY tests for Node 21 only, still not supported (#5695)

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

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

[dryrunsecurity]

DryRun Security Summary

The provided code changes update the Express.js dependency in a Node.js project from version 4.18.2 to 4.21.1, which is generally a positive change from an application security perspective, but requires reviewing the changelog and thoroughly testing the application to ensure no regressions or unintended behavior has been introduced.

Expand for full summary

Summary:

The provided code changes include updates to the package.json and package-lock.json files, which are the configuration files for a Node.js project. The key change is an update to the express dependency from version 4.18.2 to 4.21.1. From an application security perspective, this change is generally positive as it updates the Express.js framework to a newer version, which often includes security fixes and improvements. However, it's important to review the changelog or release notes for the new Express.js version to understand any significant security-related changes or improvements, and to thoroughly test the application after the dependency update to ensure no regressions or unintended behavior has been introduced.

Files Changed:

• package.json: The express dependency has been updated from version 4.18.2 to 4.21.1. Updating dependencies to newer versions is a common and recommended practice for maintaining the security and stability of a Node.js application.
• package-lock.json: Similar to the package.json file, the package-lock.json file has been updated to reflect the express dependency upgrade from version 4.18.2 to 4.21.1. This is a major version update, which could potentially introduce breaking changes or new features, so it's important to review the release notes and change log for the new version and thoroughly test the application.

Code Analysis

We ran 9 analyzers against 2 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	2 findings

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.