Skip to content

[Snyk] Security upgrade express from 4.18.1 to 4.22.0#27

Open
mandibles232 wants to merge 1 commit intomainfrom
snyk-fix-0f8d05549c030f08e7f56b54baab1131
Open

[Snyk] Security upgrade express from 4.18.1 to 4.22.0#27
mandibles232 wants to merge 1 commit intomainfrom
snyk-fix-0f8d05549c030f08e7f56b54baab1131

Conversation

@mandibles232
Copy link

snyk-top-banner

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

Snyk changed the following file(s):

  • apps/dockerapp/package.json
  • apps/dockerapp/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity 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

…o reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-QS-15268416
@mandibles232
Copy link
Author

Merge Risk: High

This upgrade to express@4.22.0 contains an erroneous breaking change that was later reverted in version 4.22.1.

Breaking Change in 4.22.0:

  • A change was introduced related to the extended query parser, which was identified as an erroneous breaking change. The GitHub release notes for version 4.22.1 explicitly state that this change was reverted. [6]

Other Notable Changes:

  • 4.20.0: The default depth for parsing URL-encoded data was changed from Infinity to 32. This could affect applications that process deeply nested objects in query strings. [4]
  • The versions between 4.18.1 and 4.22.0 also include various security fixes, bug fixes, and minor, non-breaking features. [2, 8]

Source: GitHub Release Notes

Recommendation: It is highly recommended to upgrade to express@4.22.1 or a later version to avoid the known breaking change present in 4.22.0. If you must use 4.22.0, thoroughly test functionality related to query string parsing.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants