github.com/bincyber/go-sqlcrypter vulnerable to IV collision
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-327.
Summary
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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/bincyber/go-sqlcrypter (Go) | 0.1.0 – 0.2.0 | — | No fix listed | GHSA-2j6r-9vv4-6gf5 |
- github.com/bincyber/go-sqlcrypter (Go) Vendor— Affected 0.1.0 – 0.2.0 Fixed in — No fix listed GHSA-2j6r-9vv4-6gf5
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-2j6r-9vv4-6gf5
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences