Skip to content

[Snyk] Fix for 1 vulnerabilities - #630

Open
caniszczyk wants to merge 1 commit into
masterfrom
snyk-fix-68f66103f94d6dfb6a3105991a045a26
Open

caniszczyk wants to merge 1 commit into
masterfrom
snyk-fix-68f66103f94d6dfb6a3105991a045a26

Conversation

@caniszczyk

Copy link
Copy Markdown

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):

  • package.json
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Uncaught Exception
SNYK-JS-BODYPARSER-21431495
  721  

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


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:

🦉 Uncaught Exception

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-BODYPARSER-21431495
@caniszczyk

Copy link
Copy Markdown
Author

Merge Risk: Medium

This update includes minor version bumps for body-parser and express, introducing security fixes and some behavioral changes that warrant review.

body-parser 1.20.1 → 1.20.9
This is a patch upgrade. Key changes include:

  • 1.20.3: The default depth for parsing URL-encoded data is now 32 (previously Infinity). This could affect applications processing deeply nested objects in POST requests.
  • 1.20.6: Invalid limit option values (e.g., unparseable strings) now throw an error instead of being ignored. This improves security by ensuring size limits are enforced.
  • Other versions include dependency updates and minor bug fixes.

express 4.18.2 → 4.22.0
This is a minor version upgrade within the same major version. The changes are primarily focused on security and dependency updates:

  • 4.19.0 / 4.19.1: Fixed an open redirect vulnerability.
  • 4.20.0: Fixed an XSS vulnerability.
  • 4.21.1 / 4.21.2: Updated dependencies (cookie, path-to-regexp) to address vulnerabilities.
  • 4.22.0: This version initially included a change to the query parser that was later reverted in 4.22.1 because it was an erroneous breaking change.

Recommendation:
While these upgrades do not contain major API removals, the change in body-parser's default parsing depth and stricter limit handling could impact specific use cases. It is recommended to verify that your application is not affected by these changes, especially if you handle complex, nested URL-encoded data or rely on the previous lenient behavior of the limit option. The express updates are primarily for security and should be safe to apply.

Source: body-parser Changelog, express Changelog

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

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants