NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
LOW severity

github.com/bincyber/go-sqlcrypter vulnerable to IV collisionGHSA-2j6r-9vv4-6gf5

LOWFix: bincyber/go-sqlcrypter#128

GHSA-2j6r-9vv4-6gf5 is a low-severity (CVSS 3.7) vulnerability in github.com/bincyber/go-sqlcrypter. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asGO-2024-2872
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Jun 5, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/bincyber/go-sqlcrypter

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/bincyber/go-sqlcrypter≥ 0.1.0No fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bincyber/go-sqlcrypter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of github.com/bincyber/go-sqlcrypter for GHSA-2j6r-9vv4-6gf5. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 ke
O3 Security · Impact-Aware SCA

Is GHSA-2j6r-9vv4-6gf5 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
github.com/bincyber/go-sqlcrypter vulnerable to IV collision