[GHSA-5ghq-42rg-769x] [CVE-2026-35035] - Request for CVSS correction or clarification
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- github
- 领域
- security
调研方向
从 CVE-2026-35035 的 advisory 开始，并将其已发布的 CVSS 向量与 issue 中链接的 CVSS v3.1 和 v4.0 指南进行比较。确认所提议的 UI 和影响指标是否合理；当 advisory 向量或其说明得到更正，或提供了所请求的澄清时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Hi GitHub,
Our automated CVSS enrichment pipeline detected some discrepancies between GitHub's provided vector and ours. Since this also passed a GitHub review, I thought it would be helpful to share my insights here, so that the vector or its justification might be corrected. For reference, this was the output from our AI pipeline: https://graph.volerion.com/view?id=CVE-2026-35035.
For the current vector, UI:N was set rather than UI:R, likely due to the fact that the Cross-Site Scripting payload triggers on the main landing page, but that is still considered user interaction in CVSS terms. i.e. the attacker cannot exploit this at will and user participation is required in some manner. This was later clarified in the documentation for CVSS v4.
Additionally, impact represents the delta change in capabilities and an attacker with administrator access already has complete or near-complete control over their domain, so C:H/I:H/A:H seems like an impossible stretch.
My suggestion would be to change UI:N to UI:R and C:H/I:H/A:H to C:L/I:L/A:N, which is the higher-scoring impact group taken from the subsequent browser system, rather than the potential low-integrity repudiation impact suffered by the vulnerable system.
The final vector would then be:
https://volerion.com/cvss/3.1#vector=CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
which comes down to a base score of 4.8, a serious downgrade from 9.1.
Thanks!
- 主要语言
- 没有语言数据
- 星标
- 2.5k
- 派生
- 772
- 平均合并
- 3 天 15 小时
- 30 天内合并 PR
- 46
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/advisory-database 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
github/advisory-database#9255 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
github/advisory-database#9164 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 72/100
github/advisory-database#8994 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
github/advisory-database#8898 · 4 条评论 · 1 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 72/100
github/advisory-database#8841 ·
查看 github/advisory-database 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
-
oblt-aw/detector/security
难度 2/5 1-3 小时 新手友好度 70/100
-
setup tools wizard offers no GitHub auth path, and setup summary doesn't recognize `gh` CLI auth 未关闭area/auth comp/cli P3 tool/skills type/bug
难度 2/5 1-3 小时 新手友好度 75/100
NousResearch/hermes-agent#121131 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
trailofbits/skills#330 ·
-
accepted
难度 2/5 1-3 小时 新手友好度 75/100