Summary
github.com/bincyber/go-sqlcrypter vulnerable to IV collision
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.
Impact
The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.
GHSA-2J6R-9VV4-6GF5 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2J6R-9VV4-6GF5? GHSA-2J6R-9VV4-6GF5 is a low-severity use of a broken or risky cryptographic algorithm vulnerability in github.com/bincyber/go-sqlcrypter (go), affecting versions >= 0.1.0, <= 0.2.0. No fixed version is listed yet. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
- How severe is GHSA-2J6R-9VV4-6GF5? GHSA-2J6R-9VV4-6GF5 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/bincyber/go-sqlcrypter are affected by GHSA-2J6R-9VV4-6GF5? github.com/bincyber/go-sqlcrypter (go) versions >= 0.1.0, <= 0.2.0 is affected.
- Is there a fix for GHSA-2J6R-9VV4-6GF5? No fixed version is listed for GHSA-2J6R-9VV4-6GF5 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-2J6R-9VV4-6GF5 exploitable, and should I be worried? Whether GHSA-2J6R-9VV4-6GF5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2J6R-9VV4-6GF5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2J6R-9VV4-6GF5? No fixed version is listed yet. In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.