data/reports: run fix on GO-2022-1148.yaml

This required running fix with an older version of Go because
some dependencies only work with <1.19.

Aliases: CVE-2022-23492, GHSA-j7qp-mfxf-8xjw

Updates golang/vulndb#1148

Change-Id: I5d3ada1b59f57f3f72157a367ff69028540ec05b
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/465815
Run-TryBot: Tatiana Bradley <tatianabradley@google.com>
Reviewed-by: Tim King <taking@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>

data/osv/GO-2022-1148.json

@@ -6,7 +6,7 @@
     "CVE-2022-23492",
     "GHSA-j7qp-mfxf-8xjw"
   ],
-  "details": "go-libp2p is vulnerable to targeted resource exhaustion attacks. These attacks target libp2p's connection,stream, peer, and memory management. An attacker can cause the allocation of large amounts of memory, ultimately leading to the process getting killed by the host's operating system. While a connection manager tasked with keeping the number of connections within manageable limits has been part of go-libp2p, this component was designed to handle the regular churn of peers, not a targeted resource exhaustion attack.\n\nIt's recommend that you update to v0.21.0 onwards as you'll get some useful functionality that will help in production environments like better metrics around resource usage, Grafana dashboards around resource usage, allow list support, and default autoscaling limits.",
+  "details": "go-libp2p is vulnerable to targeted resource exhaustion attacks.\n\nThese attacks target libp2p's connection, stream, peer, and memory management. An attacker can cause the allocation of large amounts of memory ultimately leading to the process getting killed by the host's operating system.\n\nWhile a connection manager tasked with keeping the number of connections within manageable limits has been part of go-libp2p, this component was designed to handle the regular churn of peers, not a targeted resource exhaustion attack.\n\nIt's recommend to update to v0.21.0 onwards to get some useful functionality that will help in production environments like better metrics around resource usage, Grafana dashboards around resource usage, allow list support, and default autoscaling limits.",
   "affected": [
     {
       "package": {
@@ -34,7 +34,12 @@
           {
             "path": "github.com/libp2p/go-libp2p",
             "symbols": [
-              "New"
+              "DefaultStaticRelays",
+              "Muxer",
+              "New",
+              "NewWithoutDefaults",
+              "Security",
+              "Transport"
             ]
           },
           {

data/reports/GO-2022-1148.yaml

@@ -7,6 +7,12 @@ modules:
       - package: github.com/libp2p/go-libp2p
         symbols:
           - New
+        derived_symbols:
+          - DefaultStaticRelays
+          - Muxer
+          - NewWithoutDefaults
+          - Security
+          - Transport
       - package: github.com/libp2p/go-libp2p/config
         symbols:
           - MuxerConstructor
@@ -52,18 +58,21 @@ modules:
           - Service.DirectConnect
           - netNotifiee.Connected
 description: |
-    go-libp2p is vulnerable to targeted resource exhaustion attacks. These
-    attacks target libp2p's connection,stream, peer, and memory management. An
-    attacker can cause the allocation of large amounts of memory, ultimately
-    leading to the process getting killed by the host's operating system. While
-    a connection manager tasked with keeping the number of connections within
-    manageable limits has been part of go-libp2p, this component was designed
-    to handle the regular churn of peers, not a targeted resource exhaustion
-    attack.
+    go-libp2p is vulnerable to targeted resource exhaustion attacks.
 
-    It's recommend that you update to v0.21.0 onwards as you'll get some useful 
-    functionality that will help in production environments like better metrics 
-    around resource usage, Grafana dashboards around resource usage, allow list 
+    These attacks target libp2p's connection, stream, peer, and memory
+    management. An attacker can cause the allocation of large amounts of memory
+    ultimately leading to the process getting killed by the host's operating
+    system.
+
+    While a connection manager tasked with keeping the number of connections
+    within manageable limits has been part of go-libp2p, this component was
+    designed to handle the regular churn of peers, not a targeted resource
+    exhaustion attack.
+
+    It's recommend to update to v0.21.0 onwards to get some useful functionality
+    that will help in production environments like better metrics around
+    resource usage, Grafana dashboards around resource usage, allow list
     support, and default autoscaling limits.
 cves:
   - CVE-2022-23492