即使使用NPM审核修复程序,我也无法修复节点漏洞-Force

发布于 2025-02-09 19:34:09 字数 1343 浏览 2 评论 0原文

亲爱的 在尝试使用NPM修复漏洞几次之后,它仍然提供下面的消息。您是否有解决这些问题的解决方案?谢谢您的帮助。

要解决所有问题,请运行: NPM审核修复 ps d:\ opencloom \ p7 \ p7 groupomania \ backend> NPM审核修复 NPM WARN配置全局- 全局- 本地已弃用。使用- 位置=全局而不是。

最新的,在2S

NPM审核报告

中审核231个包裹Glob-Parent< 5.1.2 严重性:高 正则表达拒绝在Glob-Parent中 - https://github.com/advisories/ghsa -WW39-953V-WCQ6 通过NPM审核修复程序进行修复 Node_modules/Glob-Parent Chokidar 1.0.0 -RC1-2.1.8 取决于脆弱的Glob-Parent版本 node_modules/chokidar Nodemon> = 1.3.5 取决于Chokidar的脆弱版本 取决于更新函数的脆弱版本 node_modules/nodemon

got< 11.8.5 严重性:中等 GoT允许重定向到Unix插座-g href =“ https://github.com/advisories/ghsa-pfrx-2q88-qquq97” rel =“ noreferrer”> https://github.com/advisories/ghsa-ghsa--ghsa--ghsa--ghsa--ghsa--ghsa-com-ghsa--ghsa-com-ghsa-com-ghsa-com-ghsa-com-ghsa-com-ghsa-com-ghsa-com-ghsa-com-ghsa-com一下。 PFRX-2Q88-QQ97 通过NPM审核修复程序进行修复 node_modules/got 包json< = 6.5.0 取决于易受伤害的版本 node_modules/package-json 最新版本0.2.0-5.1.0 取决于软件包JSON的脆弱版本 node_modules/最新版本 update-notifier> = 0.2.0 取决于最新版本的脆弱版本 node_modules/update-notifier

7漏洞(4中,3个高)

解决所有问题,运行: NPM审核修复 ps d:\ opencloom \ p7 \ p7 groupomania \ backend>

Dear all,
after trying several times to fix vulnerabilities with npm, it still gives the messages below; Do you have any solution to fix these problems? thank you for your help.

To address all issues, run:
npm audit fix
PS D:\openclassroom\P7\P7groupomania\backend> npm audit fix
npm WARN config global --global, --local are deprecated. Use --location=global instead.

up to date, audited 231 packages in 2s

npm audit report

glob-parent <5.1.2
Severity: high
Regular expression denial of service in glob-parent - https://github.com/advisories/GHSA-ww39-953v-wcq6
fix available via npm audit fix
node_modules/glob-parent
chokidar 1.0.0-rc1 - 2.1.8
Depends on vulnerable versions of glob-parent
node_modules/chokidar
nodemon >=1.3.5
Depends on vulnerable versions of chokidar
Depends on vulnerable versions of update-notifier
node_modules/nodemon

got <11.8.5
Severity: moderate
Got allows a redirect to a UNIX socket - https://github.com/advisories/GHSA-pfrx-2q88-qq97
fix available via npm audit fix
node_modules/got
package-json <=6.5.0
Depends on vulnerable versions of got
node_modules/package-json
latest-version 0.2.0 - 5.1.0
Depends on vulnerable versions of package-json
node_modules/latest-version
update-notifier >=0.2.0
Depends on vulnerable versions of latest-version
node_modules/update-notifier

7 vulnerabilities (4 moderate, 3 high)

To address all issues, run:
npm audit fix
PS D:\openclassroom\P7\P7groupomania\backend>

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

不再让梦枯萎 2025-02-16 19:34:10

我刚刚从GitHub Depentabot那里收到了漏洞,并通过以下方式解决了:

  1. 它看起来像是Nodemon的嵌套依赖。 https://github.com/remy/nodemon/nodemon/issues/2023 通过消除其依赖性来解决。
  2. 它是针对Nodemon的,它在开发过程中不在生产期间运行,所以您可以,我确实忽略了它,因为它不是易受伤害的代码:d。
  3. 其他选项 - 也许为您的软件包设置了一个替代。还是等到Nodemon下一个更新?

注意:有时NPM审核修复程序没有任何作用,我一直认为这是因为它不知道如何修复它,例如在Nodemon中,这是一个嵌套的依赖性,所以可能会挣扎? NPM审核修复有时可以通过升级来解决一些问题,但这会制动其他问题,因此我对此没有100%的信心。 (没有错误或文章可以支持这一点,只是轶事证据)。

I just received the got vulnerability from github dependabot, and resolved it by:

  1. It looks like it's a nested dependency of nodemon. https://github.com/remy/nodemon/issues/2023 Which they are going to fix by removing their dependency.
  2. It's for nodemon, which is run during dev not on production, so you could and I did ignore it as it's not vulnerable code :D.
  3. Other option - maybe set up an override for got in your package.json? or wait till nodemon next update?

Note: Sometimes npm audit fix does nothing, I always assumed it was because it couldn't figure out how to fix it, e.g. in nodemon it's a nested dependency so might struggle? Also npm audit fix sometimes fixes something by upgrading but that brakes something else, so I don't have 100% faith in it. (No bugs or articles to back this up, just anecdotal evidence).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文