data/reports: add GO-2024-2451.yaml

Fixes #2451

Change-Id: Ia23e653daf0f4e8dfe31885a22ddf0c649548da2
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/559217
LUCI-TryBot-Result: Go LUCI <[email protected]>
Reviewed-by: Damien Neil <[email protected]>

Author: tatianab

data/osv/GO-2024-2451.json

@@ -0,0 +1,60 @@
+{
+  "schema_version": "1.3.1",
+  "id": "GO-2024-2451",
+  "modified": "0001-01-01T00:00:00Z",
+  "published": "0001-01-01T00:00:00Z",
+  "summary": "IV collision in github.com/bincyber/go-sqlcrypter",
+  "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.",
+  "affected": [
+    {
+      "package": {
+        "name": "github.com/bincyber/go-sqlcrypter",
+        "ecosystem": "Go"
+      },
+      "ranges": [
+        {
+          "type": "SEMVER",
+          "events": [
+            {
+              "introduced": "0.1.0"
+            }
+          ]
+        }
+      ],
+      "ecosystem_specific": {
+        "imports": [
+          {
+            "path": "github.com/bincyber/go-sqlcrypter/providers/aesgcm",
+            "symbols": [
+              "New"
+            ]
+          },
+          {
+            "path": "github.com/bincyber/go-sqlcrypter/providers/awskms",
+            "symbols": [
+              "New"
+            ]
+          }
+        ]
+      }
+    }
+  ],
+  "references": [
+    {
+      "type": "REPORT",
+      "url": "https://github.com/bincyber/go-sqlcrypter/issues/127"
+    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/bincyber/go-sqlcrypter/pull/128"
+    }
+  ],
+  "credits": [
+    {
+      "name": "@takeyourhatoff"
+    }
+  ],
+  "database_specific": {
+    "url": "https://pkg.go.dev/vuln/GO-2024-2451"
+  }
+}

data/reports/GO-2024-2451.yaml

@@ -0,0 +1,31 @@
+id: GO-2024-2451
+modules:
+    - module: github.com/bincyber/go-sqlcrypter
+      versions:
+        - introduced: 0.1.0
+      vulnerable_at: 0.1.0
+      packages:
+        - package: github.com/bincyber/go-sqlcrypter/providers/aesgcm
+          symbols:
+            - New
+        - package: github.com/bincyber/go-sqlcrypter/providers/awskms
+          symbols:
+            - New
+summary: IV collision in github.com/bincyber/go-sqlcrypter
+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.
+credits:
+    - '@takeyourhatoff'
+references:
+    - report: https://github.com/bincyber/go-sqlcrypter/issues/127
+    - web: https://github.com/bincyber/go-sqlcrypter/pull/128