CVE Feed

    Dashboard / CVE / CVE-2020-8929

    CVE-2020-8929

    A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.

    Published:Oct 19, 2020
    Last Modified:Jun 5, 2025
    EPS:Oct 19, 2020
    EPSS Score:0.00081
    CVSS Score:5.3

    Affected Products

    Vendor
    Google
    Product
    Tink Java

    Exploits

    No exploit reference

    Common Attack Pattern Enumeration and Classification (CAPEC)

    CAPEC-71 Using Unicode Encoding to Bypass Validation Logic

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High