这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@Reality2byte
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade body-parser from 1.17.1 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 12 versions ahead of your current version.

  • The recommended version was released 4 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
high severity Prototype Poisoning
SNYK-JS-QS-3153490
624 Proof of Concept
low severity Regular Expression Denial of Service (ReDoS)
npm:debug:20170905
624 Proof of Concept
low severity Regular Expression Denial of Service (ReDoS)
npm:ms:20170412
624 No Known Exploit

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.17.1 to 1.20.3.

See this package in yarn:
body-parser

See this project in Snyk:
https://app.snyk.io/org/reality2byte/project/37d8c4cc-77de-42a7-8545-fa3d6cfef20a?utm_source=github&utm_medium=referral&page=upgrade-pr
@socket-security
Copy link

Report too large to display inline

View full report↗︎

@socket-security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE npm/json-schema@0.2.3 ⚠︎
Critical CVE npm/growl@1.9.2 ⚠︎
Critical CVE npm/lodash@4.17.4 ⚠︎
Critical CVE npm/deep-extend@0.4.1 ⚠︎
Critical CVE npm/babel-traverse@6.23.1 ⚠︎
Critical CVE npm/constantinople@3.1.0 ⚠︎
GitHub dependency npm/get-project-version@1.0.3 ⚠︎
Critical CVE npm/minimist@0.0.8 ⚠︎
Critical CVE npm/fsevents@1.1.1 ⚠︎
Known malware npm/fsevents@1.1.1
  • Note: This package downloads prebuilt artifacts from a domain which has been compromised. Your system may be infected if you installed this package prior to April 27, 2023
🚫

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What are GitHub dependencies?

Contains a dependency which resolves to a GitHub URL. Dependencies fetched from GitHub specifiers are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.

Publish the GitHub dependency to npm or a private package repository and consume it from there.

What is known malware?

This package is malware. We have asked the package registry to remove it.

It is strongly recommended that malware is removed from your codebase.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/json-schema@0.2.3
  • @SocketSecurity ignore npm/growl@1.9.2
  • @SocketSecurity ignore npm/lodash@4.17.4
  • @SocketSecurity ignore npm/deep-extend@0.4.1
  • @SocketSecurity ignore npm/babel-traverse@6.23.1
  • @SocketSecurity ignore npm/constantinople@3.1.0
  • @SocketSecurity ignore npm/get-project-version@1.0.3
  • @SocketSecurity ignore npm/minimist@0.0.8
  • @SocketSecurity ignore npm/fsevents@1.1.1

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