Vulnerabilities in pkg:golang/github.com/bincyber/go-sqlcrypter

PACKAGE
Advisory Summary

GHSA-2j6r-9vv4-6gf5 is a LOW (CVSS 3.7) github.com/bincyber/go-sqlcrypter vulnerable to iv collision vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Github.com/bincyber/go sqlcrypter libraries in the Go ecosystem. The issue involves github.com/bincyber/go-sqlcrypter vulnerable to iv collision. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

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

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/bincyber/go-sqlcrypter. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-2j6r-9vv4-6gf5 - LOW github.com/bincyber/go-sqlcrypter vulnerable to IV collision

GHSA-2j6r-9vv4-6gf5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2j6r-9vv4-6gf5
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Github.com/bincyber/go sqlcrypter
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-2j6r-9vv4-6gf5

To remediate this vulnerability, upgrade all affected Github.com/bincyber/go sqlcrypter dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/bincyber/go-sqlcrypter fixed: Latest secure release
Upgrade github.com/bincyber/go-sqlcrypter to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/bincyber/go-sqlcrypter

How to Check if You Are Affected

To determine whether your application is affected by GHSA-2j6r-9vv4-6gf5, inspect your project dependencies for Github.com/bincyber/go sqlcrypter:

inspect dependencies for github.com/bincyber/go-sqlcrypter

Analyze the terminal output to locate any version of Github.com/bincyber/go sqlcrypter in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Github.com/bincyber/go sqlcrypter, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-2j6r-9vv4-6gf5 Affected Github.com/bincyber/go sqlcrypter Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
github.com/bincyber/go-sqlcrypter
Go
≥ 0.1.0
≤ 0.2.0

References

Frequently Asked Questions

What is GHSA-2j6r-9vv4-6gf5?
GHSA-2j6r-9vv4-6gf5 is a security vulnerability in Github.com/bincyber/go sqlcrypter involving github.com/bincyber/go-sqlcrypter vulnerable to IV collision under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Github.com/bincyber/go sqlcrypter versions are affected?
Affected versions include releases prior to current release patches across affected packages: github.com/bincyber/go-sqlcrypter.
What version fixes GHSA-2j6r-9vv4-6gf5?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/bincyber/go-sqlcrypter affected?
Yes, github.com/bincyber/go-sqlcrypter is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-2j6r-9vv4-6gf5?
GHSA-2j6r-9vv4-6gf5 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with GHSA-2j6r-9vv4-6gf5?
GHSA-2j6r-9vv4-6gf5 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check Go dependencies for GHSA-2j6r-9vv4-6gf5?
Run the dependency tree command: 'inspect dependencies for github.com/bincyber/go-sqlcrypter'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2j6r-9vv4-6gf5",
  "modified" : "2024-05-20T21:56:07Z",
  "published" : "2024-05-20T21:56:07Z",
  "aliases" : [ ],
  "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.\n\nThe 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" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/bincyber/go-sqlcrypter"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.1.0"
      }, {
        "last_affected" : "0.2.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bincyber/go-sqlcrypter/issues/127"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bincyber/go-sqlcrypter/pull/128"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/bincyber/go-sqlcrypter/commit/96c73cd2b8fd15c9da9b3eafe62c9a040f6537e8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bincyber/go-sqlcrypter"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2024-2451"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-20T21:56:07Z",
    "nvd_published_at" : null
  }
}