Repository navigation
go.temporal.io/sdk-v1.14.0: 1 vulnerabilities (highest severity is: 7.5) #17
Description
Activity
- changed the title
[-]go.temporal.io/sdk-v1.14.0: 3 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 4 vulnerabilities (highest severity is: 7.5)[/+]on Sep 20, 2022 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 4 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 1 vulnerabilities (highest severity is: 7.5)[/+]on Oct 28, 2022 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 1 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 2 vulnerabilities (highest severity is: 7.5)[/+]on Dec 7, 2022 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 2 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 1 vulnerabilities (highest severity is: 5.3)[/+]on Jan 6, 2023 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 1 vulnerabilities (highest severity is: 5.3)[/-][+]go.temporal.io/sdk-v1.14.0: 6 vulnerabilities (highest severity is: 7.5)[/+]on Jan 6, 2023 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 6 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 7 vulnerabilities (highest severity is: 7.5)[/+]on Jan 23, 2023 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 7 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 6 vulnerabilities (highest severity is: 7.5)[/+]on Jun 9, 2023 - changed the title
[-]go.temporal.io/sdk-v1.14.0: 6 vulnerabilities (highest severity is: 7.5)[/-][+]go.temporal.io/sdk-v1.14.0: 6 vulnerabilities (highest severity is: 7.5) - autoclosed[/+]on Jul 10, 2023 ✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
- changed the title
[-]go.temporal.io/sdk-v1.14.0: 6 vulnerabilities (highest severity is: 7.5) - autoclosed[/-][+]go.temporal.io/sdk-v1.14.0: 1 vulnerabilities (highest severity is: 7.5)[/+]on Oct 20, 2023 ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.
Path to dependency file: /activity_worker/go_workflow/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/net/@v/v0.7.0.mod
Found in HEAD commit: ac44173063e14aaf5e2fd3eca9caf9197f4d6dd5
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - golang.org/x/net-v0.7.0
Library home page: https://proxy.golang.org/golang.org/x/net/@v/v0.7.0.zip
Path to dependency file: /activity_worker/go_workflow/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/net/@v/v0.7.0.mod
Dependency Hierarchy:
Found in HEAD commit: ac44173063e14aaf5e2fd3eca9caf9197f4d6dd5
Found in base branch: main
Vulnerability Details
A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.
Publish Date: 2023-10-11
URL: CVE-2023-39325
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://pkg.go.dev/vuln/GO-2023-2102
Release Date: 2023-10-11
Fix Resolution: go1.20.10, go1.21.3, golang.org/x/net - v0.17.0