Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Snyk] Upgrade body-parser from 1.9.0 to 1.20.3 #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

UgoOluwa
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade body-parser from 1.9.0 to 1.20.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 38 versions ahead of your current version.

  • The recommended version was released on 2 months ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Asymmetric Resource Consumption (Amplification)
SNYK-JS-BODYPARSER-7926860
624 No Known Exploit
Release notes
Package name: body-parser
  • 1.20.3 - 2024-09-09

    What's Changed

    Important

    • deps: qs@6.13.0
    • add depth option to customize the depth level in the parser
    • IMPORTANT: The default depth level for parsing URL-encoded data is now 32 (previously was Infinity). Documentation

    Other changes

    New Contributors

    Full Changelog: 1.20.2...1.20.3

  • 1.20.2 - 2023-02-22
    • Fix strict json error message on Node.js 19+
    • deps: content-type@~1.0.5
      • perf: skip value escaping when unnecessary
    • deps: raw-body@2.5.2
  • 1.20.1 - 2022-10-06
    • deps: qs@6.11.0
    • perf: remove unnecessary object clone
  • 1.20.0 - 2022-04-03
    • Fix error message for json parse whitespace in strict
    • Fix internal error when inflated body exceeds limit
    • Prevent loss of async hooks context
    • Prevent hanging when request already read
    • deps: depd@2.0.0
      • Replace internal eval usage with Function constructor
      • Use instance methods on process to check for listeners
    • deps: http-errors@2.0.0
      • deps: depd@2.0.0
      • deps: statuses@2.0.1
    • deps: on-finished@2.4.1
    • deps: qs@6.10.3
    • deps: raw-body@2.5.1
      • deps: http-errors@2.0.0
  • 1.19.2 - 2022-02-16
    • deps: bytes@3.1.2
    • deps: qs@6.9.7
      • Fix handling of __proto__ keys
    • deps: raw-body@2.4.3
      • deps: bytes@3.1.2
  • 1.19.1 - 2021-12-10
  • 1.19.0 - 2019-04-26
  • 1.18.3 - 2018-05-14
  • 1.18.2 - 2017-09-22
  • 1.18.1 - 2017-09-12
  • 1.18.0 - 2017-09-09
  • 1.17.2 - 2017-05-18
  • 1.17.1 - 2017-03-06
  • 1.17.0 - 2017-03-01
  • 1.16.1 - 2017-02-11
  • 1.16.0 - 2017-01-18
  • 1.15.2 - 2016-06-20
  • 1.15.1 - 2016-05-06
  • 1.15.0 - 2016-02-11
  • 1.14.2 - 2015-12-16
  • 1.14.1 - 2015-09-28
  • 1.14.0 - 2015-09-16
  • 1.13.3 - 2015-07-31
  • 1.13.2 - 2015-07-06
  • 1.13.1 - 2015-06-16
  • 1.13.0 - 2015-06-15
  • 1.12.4 - 2015-05-11
  • 1.12.3 - 2015-04-16
  • 1.12.2 - 2015-03-17
  • 1.12.1 - 2015-03-16
  • 1.12.0 - 2015-02-14
  • 1.11.0 - 2015-01-31
  • 1.10.2 - 2015-01-21
  • 1.10.1 - 2015-01-02
  • 1.10.0 - 2014-12-03
  • 1.9.3 - 2014-11-22
  • 1.9.2 - 2014-10-28
  • 1.9.1 - 2014-10-23
  • 1.9.0 - 2014-09-24
from body-parser GitHub release notes

Important

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

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade body-parser from 1.9.0 to 1.20.3.

See this package in npm:
body-parser

See this project in Snyk:
https://app.snyk.io/org/ugooluwa/project/aae104c1-d6b8-47f1-b8aa-ffedb9c7b230?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants