Composer reports advisory for flysystem

未关闭
#41,877 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
php
领域
security

调研方向

Start with composer.json and the linked Dependabot report and Flysystem advisories; confirm which Flysystem version is resolved and whether the reported vulnerabilities apply to ownCloud Classic. Then identify an appropriate action for the affected dependency and verify the Composer security-audit result is addressed.

由索引模型根据 Issue 内容生成。

描述

composer is reporting a new vulnerability in https://github.com/thephpleague/flysystem

https://github.com/advisories/GHSA-cxf4-7mrp-vvpr

https://github.com/owncloud/core/security/dependabot/101

Check the report and see if it is applicable to ownCloud Classic, and take appropriate action.
Note: the advisory is fixed in major version 3, core still references major version 1.

$ composer update
[bamarni-bin] The setting "extra.bamarni-bin.forward-command" will be set to "true" from 2.x onwards. If you wish to keep it to "false", you need to set it explicitly.
Loading composer repositories with package information
Updating dependencies                                 
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires league/flysystem ^1.1, found league/flysystem[1.1.0, ..., 1.1.10] but these were not loaded, because they are affected by security advisories ("PKSA-w9tt-7782-78jx", "PKSA-pwh8-d4fr-nywn"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.

The 2nd one reported is actually fixed in the flysystem version that we are using. Not sure why composer referenced that.
https://github.com/thephpleague/flysystem/security/advisories/GHSA-9f46-5r25-5wfm

主要语言
PHP
星标
8.8k
派生
2.1k
平均合并
19 小时 32 分钟
30 天内合并 PR
56

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

owncloud/core 的其他 Issue

查看 owncloud/core 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。