Skip to content

🚨 [security] Update body-parser 1.19.0 → 2.2.1 (major) #35

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

🚨 [security] Update body-parser 1.19.0 → 2.2.1 (major) #35

wants to merge 1 commit into from

Conversation

@depfu
Copy link

@depfu depfu bot commented Nov 25, 2025

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ body-parser (1.19.0 → 2.2.1) · Repo · Changelog

Security Advisories 🚨

🚨 body-parser is vulnerable to denial of service when url encoding is used

Impact

body-parser 2.2.0 is vulnerable to denial of service due to inefficient handling of URL-encoded bodies with very large numbers of parameters. An attacker can send payloads containing thousands of parameters within the default 100KB request size limit, causing elevated CPU and memory usage. This can lead to service slowdown or partial outages under sustained malicious traffic.

Patches

This issue is addressed in version 2.2.1.

🚨 body-parser vulnerable to denial of service when url encoding is enabled

Impact

body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service.

Patches

this issue is patched in 1.20.3

References

Release Notes

2.2.0

What's Changed

New Contributors

Full Changelog: v2.1.0...v2.2.0

2.0.0

What's Changed

Important

  • add brotli support #406
  • Breaking Change: Node.js 18 is the minimum supported version

Details

New Contributors

Full Changelog: 1.20.2...2.0.0

1.20.3

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

  • 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 (from changelog)

  • deps: qs@6.11.0
  • perf: remove unnecessary object clone

1.20.0

  • 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

  • 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

  • deps: bytes@3.1.1
  • deps: http-errors@1.8.1
    • deps: inherits@2.0.4
    • deps: toidentifier@1.0.1
    • deps: setprototypeof@1.2.0
  • deps: qs@6.9.6
  • deps: raw-body@2.4.2
    • deps: bytes@3.1.1
    • deps: http-errors@1.8.1
  • deps: safe-buffer@5.2.1
  • deps: type-is@~1.6.18

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ bytes (indirect, 3.1.0 → 3.1.2) · Repo · Changelog

Release Notes

3.1.2 (from changelog)

  • Fix return value for un-parsable strings

3.1.1 (from changelog)

  • Fix "thousandsSeparator" incorrecting formatting fractional part

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 33 commits:

↗️ iconv-lite (indirect, 0.4.24 → 0.7.0) · Repo · Changelog

Release Notes

0.7.0

🐞 Bug fixes

  • Handle split surrogate pairs when encoding utf8 - by @yosion-p and @ashtuchkin in #282:

    Handle a case where streaming utf8 encoder (converting js strings -> buffers) encounters
    surrogate pairs split between chunks (last character of one chunk is high surrogate and first
    character of the next chunk is a low surrogate).

  • Avoid false positives in encodingExists by using objects without a prototype - by @bjohansebas in #328

    The encodingExists method could return incorrect results if the lookup matched properties inherited
    from the prototype of the object that stores the encodings, such as constructor and others. This change
    replaces that object with one that has no prototype, ensuring that only explicitly defined valid encodings
    in the library are considered. In addition, the fix is applied to the internal cache system to avoid the same
    kind of false positives

🚀 Improvements

  • Make explicit that decode() method supports Uint8Array input - by @jardicc in #271
  • Remove compatibility check for StringDecoder.end method - by @bjohansebas in #331

Other changes

New Contributors

Full Changelog: pillarjs/iconv-lite@v0.6.3...v0.7.0

0.6.3 (from changelog)

  • Fix HKSCS encoding to prefer Big5 codes if both Big5 and HKSCS codes are possible (#264)

0.6.2 (from changelog)

  • Support Uint8Array-s decoding without conversion to Buffers, plus fix an edge case.

0.6.1 (from changelog)

  • Support Uint8Array-s directly when decoding (#246, by @gyzerok)
  • Unify package.json version ranges to be strictly semver-compatible (#241)
  • Fix minor issue in UTF-32 decoder's endianness detection code.

0.6.0 (from changelog)

  • Updated 'gb18030' encoding to :2005 edition (see whatwg/encoding#22).
  • Removed iconv.extendNodeEncodings() mechanism. It was deprecated 5 years ago and didn't work in recent Node versions.
  • Reworked Streaming API behavior in browser environments to fix #204. Streaming API will be excluded by default in browser packs, saving ~100Kb bundle size, unless enabled explicitly using iconv.enableStreamingAPI(require('stream')).
  • Updates to development environment & tests:
    • Added ./test/webpack private package to test complex new use cases that need custom environment. It's tested as a separate job in Travis CI.
    • Updated generation code for the new EUC-KR index file format from Encoding Standard.
    • Removed Buffer() constructor in tests (#197 by @gabrielschulhof).

0.5.2 (from changelog)

  • Added iconv.getEncoder() and iconv.getDecoder() methods to typescript definitions (#229).
  • Fixed semver version to 6.1.2 to support Node 8.x (by @Tanandara).
  • Capped iconv version to 2.x as 3.x has dropped support for older Node versions.
  • Switched from instanbul to c8 for code coverage.

0.5.1 (from changelog)

  • Added cp720 encoding (#221, by @kr-deps)
  • (minor) Changed Changelog.md formatting to use h2.

0.5.0 (from changelog)

  • Added UTF-32 encoding, both little-endian and big-endian variants (UTF-32LE, UTF32-BE). If endianness is not provided for decoding, it's deduced automatically from the stream using a heuristic similar to what we use in UTF-16. (great work in #216 by @kshetline)
  • Several minor updates to README (#217 by @oldj, plus some more)
  • Added Node versions 10 and 12 to Travis test harness.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 51 commits:

↗️ raw-body (indirect, 2.4.0 → 3.0.2) · Repo · Changelog

Release Notes

3.0.2

What's Changed

  • docs: enhance security reporting and disclosure procedures by @bjohansebas in #101

  • ci: add workflows for CodeQL analysis and Scorecard security checks, update dependabot configuration and Node.js versions by @bjohansebas in #102

  • deps: use tilde notation for dependencies by @Phillip9587 in #120

  • chore: remove history.md and security.md from being packaged on publish by @bjohansebas in #122

  • build(deps): bump github/codeql-action from 3.30.5 to 4.31.0 by @dependabot[bot] in #105

  • build(deps): bump actions/checkout from 4 to 5 by @dependabot[bot] in #107

  • build(deps): bump actions/upload-artifact from 4 to 5 by @dependabot[bot] in #110

  • chore: use neostandard by @bjohansebas in #116

  • build(deps): bump actions/download-artifact from 4 to 6 by @dependabot[bot] in #108

  • build(deps): bump actions/setup-node from 4 to 6 by @dependabot[bot] in #118

  • build(deps): bump actions/checkout from 4 to 5 by @dependabot[bot] in #119

  • build(deps): bump github/codeql-action from 4.31.0 to 4.31.2 by @dependabot[bot] in #117

  • release: 3.0.2 by @bjohansebas in #123

New Contributors

Full Changelog: v3.0.1...v3.0.2

3.0.1

What's Changed

New Contributors

Full Changelog: v3.0.0...v3.0.1

3.0.0 (from changelog)

  • deps: iconv-lite@0.6.3
    • Fix HKSCS encoding to prefer Big5 codes
    • Fix minor issue in UTF-32 decoder's endianness detection code
    • Update 'gb18030' encoding to :2005 edition

2.5.2 (from changelog)

  • Fix error message for non-stream argument

2.5.1 (from changelog)

  • Fix error on early async hooks implementations

2.5.0 (from changelog)

  • Prevent loss of async hooks context
  • Prevent hanging when stream is not readable
  • deps: http-errors@2.0.0
    • deps: depd@2.0.0
    • deps: statuses@2.0.1

2.4.3 (from changelog)

  • deps: bytes@3.1.2

2.4.2 (from changelog)

  • deps: bytes@3.1.1
  • deps: http-errors@1.8.1
    • deps: setprototypeof@1.2.0
    • deps: toidentifier@1.0.1

2.4.1 (from changelog)

  • deps: http-errors@1.7.3
    • deps: inherits@2.0.4

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 call-bind-apply-helpers (added, 1.0.2)

🆕 call-bound (added, 1.0.4)

🆕 dunder-proto (added, 1.0.1)

🆕 es-define-property (added, 1.0.1)

🆕 es-errors (added, 1.3.0)

🆕 es-object-atoms (added, 1.1.1)

🆕 function-bind (added, 1.1.2)

🆕 get-intrinsic (added, 1.3.0)

🆕 get-proto (added, 1.0.1)

🆕 gopd (added, 1.2.0)

🆕 has-symbols (added, 1.1.0)

🆕 hasown (added, 2.0.2)

🆕 math-intrinsics (added, 1.1.0)

🆕 object-inspect (added, 1.13.4)

🆕 side-channel (added, 1.1.0)

🆕 side-channel-list (added, 1.0.0)

🆕 side-channel-map (added, 1.0.1)

🆕 side-channel-weakmap (added, 1.0.2)

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant