Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Advisory version ranges still flag 3.2.0 as vulnerable (GHSA-j3p4-wp97-rph4, GHSA-j9gm-c75j-xc9q, GHSA-jjfr-hcj7-qf5w, GHSA-wmxv-xphr-5c9g, GHSA-gwg2-r3hj-4w44)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
csharp, github
领域
security

调研方向

Start by reading the referenced fix in #3208 and related issue #3205, then check how these five advisories define affected and patched versions. The requested change is to update their ranges so 3.2.0 is recognized as patched while versions below 3.2.0 and the affected 4.x range remain covered; done when NuGet audit no longer reports 3.2.0 for these advisories.

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

描述

ImageSharp 3.2.0 backports the fixes for these advisories (#3208), but the GitHub Advisory Database entries still list the affected range as >= 2.0.0, <= 4.1.1 with 4.1.2 as the only patched version.

As a result, NuGet audit (NU1902/NU1903) reports 3.2.0 as vulnerable, which fails builds that use TreatWarningsAsErrors and pushes consumers toward suppressions or a major-version upgrade.

Could the advisory ranges be updated to < 3.2.0 || >= 4.0.0, < 4.1.2 (with 3.2.0 listed as a patched version) for these five advisories? Related: #3205.

https://www.nuget.org/packages/SixLabors.ImageSharp/3.2.0

Image
主要语言
C#
星标
8k
派生
904
平均合并
15 小时 39 分钟
30 天内合并 PR
12

环境准备

从这里开始

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

SixLabors/ImageSharp 的其他 Issue

查看 SixLabors/ImageSharp 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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