GO-2024-2451

    Dashboard / Vulnerabilities / GO-2024-2451

    GO-2024-2451

    Published: 30 Jan 2024Last Modified: 20 May 2024

    Summary: IV collision in github.com/bincyber/go-sqlcrypter

    Details: There is a risk of an IV collision using the awskms or aesgcm provider. NIST SP 800-38D section 8.3 states that it is unsafe to encrypt more than 2^32 plaintexts under the same key when using a random IV. The limit could easily be reached given the use case of database column encryption. Ciphertexts are likely to be persisted and stored together. IV collision could enable an attacker with access to the ciphertexts to decrypt all messages encrypted with the affected key. The aesgcm provider cannot be fixed without a breaking change, so users should not encrypt more than 2^32 values with any key. The awskms package can be fixed without a breaking change by switching to a counter-based IV.

    Affected packages

    Package

    Name: github.com/bincyber/go-sqlcrypter

    Purl: pkg:golang/github.com/bincyber/go-sqlcrypter

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.1.0
    Fixed -None

    Affected versions

    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
    GO-2024-2451 | CVE-DB