data/reports: add GO-2024-2870

  - data/reports/GO-2024-2870.yaml

Fixes golang/vulndb#2870

Change-Id: Ie430468d1dd0eebcfbbb67de97dc44849671523a
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/587395
Run-TryBot: Zvonimir Pavlinovic <zpavlinovic@google.com>
Reviewed-by: Tatiana Bradley <tatianabradley@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
diff --git a/data/osv/GO-2024-2870.json b/data/osv/GO-2024-2870.json
new file mode 100644
index 0000000..0d45d7d
--- /dev/null
+++ b/data/osv/GO-2024-2870.json
@@ -0,0 +1,71 @@
+{
+  "schema_version": "1.3.1",
+  "id": "GO-2024-2870",
+  "modified": "0001-01-01T00:00:00Z",
+  "published": "0001-01-01T00:00:00Z",
+  "aliases": [
+    "CVE-2024-35192",
+    "GHSA-xcq4-m2r3-cmrj"
+  ],
+  "summary": "Credential leakage in github.com/aquasecurity/trivy",
+  "details": "A malicious registry can cause Trivy to leak credentials for legitimate registries such as AWS Elastic Container Registry (ECR), Google Cloud Artifact/Container Registry, or Azure Container Registry (ACR) if the registry is scanned from directly using Trivy. These tokens can then be used to push/pull images from those registries to which the identity/user running Trivy has access. This vulnerability only applies when scanning container images directly from a registry. If you use Docker, containerd or other runtime to pull images locally and scan them with Trivy, you are not affected. To enforce this behavior, you can use the --image-src flag to select which sources you trust.",
+  "affected": [
+    {
+      "package": {
+        "name": "github.com/aquasecurity/trivy",
+        "ecosystem": "Go"
+      },
+      "ranges": [
+        {
+          "type": "SEMVER",
+          "events": [
+            {
+              "introduced": "0"
+            },
+            {
+              "fixed": "0.51.2"
+            }
+          ]
+        }
+      ],
+      "ecosystem_specific": {
+        "imports": [
+          {
+            "path": "github.com/aquasecurity/trivy/pkg/fanal/image/registry/azure"
+          },
+          {
+            "path": "github.com/aquasecurity/trivy/pkg/fanal/image/registry/ecr",
+            "symbols": [
+              "ECR.CheckOptions"
+            ]
+          },
+          {
+            "path": "github.com/aquasecurity/trivy/pkg/fanal/image/registry/google",
+            "symbols": [
+              "Registry.CheckOptions"
+            ]
+          }
+        ]
+      }
+    }
+  ],
+  "references": [
+    {
+      "type": "ADVISORY",
+      "url": "https://github.com/aquasecurity/trivy/security/advisories/GHSA-xcq4-m2r3-cmrj"
+    },
+    {
+      "type": "FIX",
+      "url": "https://github.com/aquasecurity/trivy/commit/e7f14f729de259551203f313e57d2d9d3aa2ff87"
+    }
+  ],
+  "credits": [
+    {
+      "name": "@lyoung-confluent"
+    }
+  ],
+  "database_specific": {
+    "url": "https://pkg.go.dev/vuln/GO-2024-2870",
+    "review_status": "REVIEWED"
+  }
+}
\ No newline at end of file
diff --git a/data/reports/GO-2024-2870.yaml b/data/reports/GO-2024-2870.yaml
new file mode 100644
index 0000000..874f28f
--- /dev/null
+++ b/data/reports/GO-2024-2870.yaml
@@ -0,0 +1,38 @@
+id: GO-2024-2870
+modules:
+    - module: github.com/aquasecurity/trivy
+      versions:
+        - fixed: 0.51.2
+      vulnerable_at: 0.51.1
+      packages:
+        - package: github.com/aquasecurity/trivy/pkg/fanal/image/registry/azure
+        - package: github.com/aquasecurity/trivy/pkg/fanal/image/registry/ecr
+          symbols:
+            - ECR.CheckOptions
+        - package: github.com/aquasecurity/trivy/pkg/fanal/image/registry/google
+          symbols:
+            - Registry.CheckOptions
+summary: Credential leakage in github.com/aquasecurity/trivy
+description: |-
+    A malicious registry can cause Trivy to leak credentials for legitimate
+    registries such as AWS Elastic Container Registry (ECR), Google Cloud
+    Artifact/Container Registry, or Azure Container Registry (ACR) if the registry
+    is scanned from directly using Trivy. These tokens can then be used to push/pull
+    images from those registries to which the identity/user running Trivy has
+    access. This vulnerability only applies when scanning container images directly
+    from a registry. If you use Docker, containerd or other runtime to pull images
+    locally and scan them with Trivy, you are not affected. To enforce this
+    behavior, you can use the --image-src flag to select which sources you trust.
+cves:
+    - CVE-2024-35192
+ghsas:
+    - GHSA-xcq4-m2r3-cmrj
+credits:
+    - '@lyoung-confluent'
+references:
+    - advisory: https://github.com/aquasecurity/trivy/security/advisories/GHSA-xcq4-m2r3-cmrj
+    - fix: https://github.com/aquasecurity/trivy/commit/e7f14f729de259551203f313e57d2d9d3aa2ff87
+source:
+    id: GHSA-xcq4-m2r3-cmrj
+    created: 2024-05-22T14:41:45.135631743Z
+review_status: REVIEWED