- 受影響的版本
- Java 的 Tink 1.0 - 1.3.x 版
- Android 上的 Tink 版本 1.0 - 1.3.x
- Golang 上的 Tink 1.0 - 1.3.x 版本
- 受影響的金鑰類型
- AES-GCM-HKDF
說明
串流 AEAD 實作會加密區隔中的明文。Tink 會使用 4 位元組的區段計數器。加密包含超過 232 個區段的串流時，區段計數器可能會溢位，並導致金鑰內容或純文字外洩。
串流 AEAD 溢位
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：2025-07-25 (世界標準時間)。"],[[["\u003cp\u003eTink versions 1.0 to 1.3.x on Java, Android, and Golang are impacted by a security vulnerability.\u003c/p\u003e\n"],["\u003cp\u003eThe vulnerability affects the AES-GCM-HKDF key type when used with Streaming AEAD.\u003c/p\u003e\n"],["\u003cp\u003eEncrypting large data streams (over 2^32^ segments) with the vulnerable versions can lead to key material or plaintext leakage due to a segment counter overflow.\u003c/p\u003e\n"]]],["Tink versions 1.0-1.3.x on Java, Android, and Golang are affected, specifically with AES-GCM-HKDF key types. The issue arises in Streaming AEAD implementations where data is encrypted in segments. When a stream exceeds 2^32 segments, the 4-byte segment counter overflows. This overflow can potentially cause the leakage of key material or plaintext.\n"],null,["# Streaming AEAD overflow\n\nAffected Versions\n: Tink version 1.0 - 1.3.x on Java\n: Tink version 1.0 - 1.3.x on Android\n: Tink version 1.0 - 1.3.x on Golang\n\nAffected Key Types\n: AES-GCM-HKDF\n\nDescription\n-----------\n\n[Streaming AEAD](/tink/streaming-aead) implementations encrypt the plaintext in\nsegments. Tink uses a 4-byte segment counter. When encrypting a stream\nconsisting of more than 2^32^ segments, the segment counter might\noverflow and lead to leakage of key material or plaintext."]]