Data quality issue with CVE-2026-11460

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The payload names no source file or test, so start by locating where CVE-2026-11460's affected version ranges are stored or generated in the osv.dev repository. The problem is that Boost versions are recorded as X.YY where upstream uses X.YY.Z. The suggested fixes are a manual data correction or a conversation with the CNA, and the maintainers have not chosen between them. Done means a decision on the approach and a corrected record, which needs maintainer input first.

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

描述

data quality

The CVE ID

https://osv.dev/vulnerability/CVE-2026-11460

Describe the data quality issue observed

All versions listed are of the form X.YY, e.g. 1.61.

Unfortunately, that's not how boost is versioned: boost releases are all of the form X.YY.Z (e.g., 1.61.0).
See https://github.com/boostorg/boost/releases

Suggested changes to record

Stupid fix: manually tag a .0 on the end of all the versions. That works for boost vulnerabilities, but nothing else.

Possibly better fix: go talk to the CNA (VulDB?)

Additional context

主要语言
Go
星标
3k
派生
390
平均合并
22 小时 24 分钟
30 天内合并 PR
125

环境准备

从这里开始

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

google/osv.dev 的其他 Issue

查看 google/osv.dev 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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