Advisory

GHSA-2j6r-9vv4-6gf5

Also known as: GO-2024-2872

Summary

github.com/bincyber/go-sqlcrypter vulnerable to IV collision

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-05-20 21:56 UTC
Modified
2024-06-05 16:43 UTC

Affected packages and fixes

github.com/bincyber/go-sqlcrypter

Go · All systems

Affected

  • introduced 0.1.0, last affected 0.2.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences