安全速报自动同步 · 保留上游原文

【中危】snipe-it 安全更新(GHSA-mr8g-2mj4-pcq2)

S
KHack 安全情报
2026/6/24 发布 · 8 阅读

安全情报快照 · 风险级别:中危 · CVSS:5.9 · CVE-2026-49870 · GHSA-mr8g-2mj4-pcq2

先看结论

snipe-it存在安全风险,< 8.6.0 受影响,建议升级至 8.6.0。

影响范围

生态 组件 受影响版本 首个修复版本
composer snipe/snipe-it < 8.6.0 8.6.0

处置建议

优先将 snipe/snipe-it 升级至 8.6.0 或更高版本;升级前请结合业务依赖完成兼容性验证。

上游技术详情(原文)

Impact

POST /two-factor had no rate limiting, lockout, or attempt counter. An attacker with valid credentials can submit unlimited TOTP guesses. The TOTP implementation accepts the current code plus one step on either side (config/google2fa.php window=1), so at any instant 3 of 1,000,000 codes are accepted.

After a correct guess the attacker holds a fully authenticated session. If the instance is configured with 2FA in optional mode (two_factor_enabled='1'), the attacker can additionally disable 2FA via POST /account/profile with two_factor_optin=0. No OTP re-verification is required. The account is then accessible with the password alone on future logins. If 2FA is in required-for-all mode (='2'), the per-user opt-out path is closed and the impact stops at session-level account takeover. For an admin target, POST /api/v1/users/two_factor_reset additionally clears another user's 2FA secret.

Patches

Patched in v8.6.0

来源与许可

本页自动同步 GitHub Advisory Database 的公开数据,并保留上游原文供核验;不宣称原创分析。数据许可:CC-BY-4.0。

评论

还没有评论,来说两句。