POJIA破甲
地图 / Constant-time comparison is not always implemented; critical areas are vulnerable to key-timing attacks

Constant-time comparison is not always implemented; critical areas are vulnerable to key-timing attacks

密码学缺陷 / Missing Required Cryptographic Step / #363680

厂商
Monero
严重程度
高危
赏金
—
弱点
Missing Required Cryptographic Step
研究员
@anonimal
披露日期
2018-08-06
资产
—
CVE
—

该报告还没有中文解读。

原文摘录

摘自原文(2154 字符中的一小部分)
In my most superficial of reviews, constant-time comparison appears to not be globally implemented (at a glance, only implemented within the ref10 implementation).

默认不展示报告全文。以上为简短摘录,完整复现过程请阅读原文。版权归研究员与 Monero 所有。

时间线

  • 报告提交
  • 公开披露
阅读 HackerOne 原文 ↗作者 @anonimal · 版权归作者与 Monero 所有

同类报告

HMAC signature verification omits endpoint and payload allowing request forgery on CoinMate APICoinMate.io · 2026-05-20`check_reserve_proof` sums RingCT ECDH amounts without checking the output commitmentMonero · 2026-08-05SSL options ISSUERCERT, EC_CURVES and CRLFILE silently ignored by non-OpenSSL backendscurl · 2026-01-20SpendProofV1 txid-substitution: get_spend_proof/check_spend_proof do not verify returned transaction hashMonero · 2026-08-05Missing AES-GCM Authentication Tag Validation and Improper Deprecation HandlingNode.js · 2025-12-19Phabricator is vulnerable to padding oracle attacks and chosen-ciphertext attacks.Phabricator · 2017-04-05 · $750