Closed mend-for-github-com[bot] closed 9 months ago
cc: @rblcoder @afrodidact
Add @prudhvigodithi on more information about this.
The fix is not yet merged https://github.com/aws/aws-sdk-go/issues/4738
:heavy_check_mark: 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.
Found in HEAD commit: b33b9cb47d3992246b64ee4aab440f2d0987e644
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
CVE-2023-39325
### Vulnerable Library - golang.org/x/net-v0.1.0[mirror] Go supplementary network libraries
Library home page: https://proxy.golang.org/golang.org/x/net/@v/v0.1.0.zip
Dependency Hierarchy: - github.com/aws/aws-Sdk-go-v1.45.24 (Root Library) - :x: **golang.org/x/net-v0.1.0** (Vulnerable Library)
Found in HEAD commit: b33b9cb47d3992246b64ee4aab440f2d0987e644
Found in base branch: main
### Vulnerability DetailsA 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 FixType: 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
CVE-2022-41721
### Vulnerable Library - golang.org/x/net-v0.1.0[mirror] Go supplementary network libraries
Library home page: https://proxy.golang.org/golang.org/x/net/@v/v0.1.0.zip
Dependency Hierarchy: - github.com/aws/aws-Sdk-go-v1.45.24 (Root Library) - :x: **golang.org/x/net-v0.1.0** (Vulnerable Library)
Found in HEAD commit: b33b9cb47d3992246b64ee4aab440f2d0987e644
Found in base branch: main
### Vulnerability DetailsA request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.
Publish Date: 2023-01-13
URL: CVE-2022-41721
### 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 FixType: Upgrade version
Release Date: 2023-01-13
Fix Resolution: v0.2.0