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.
                
            References
                    Configurations
                    Configuration 1 (hide)
            
            
  | 
    
Configuration 2 (hide)
            
            
  | 
    
Configuration 3 (hide)
            
            
  | 
    
History
                    No history.
Information
                Published : 2023-10-11 22:15
Updated : 2024-04-28 04:15
NVD link : CVE-2023-39325
Mitre link : CVE-2023-39325
CVE.ORG link : CVE-2023-39325
JSON object : View
Products Affected
                golang
- go
 - http2
 
fedoraproject
- fedora
 
netapp
- astra_trident
 - astra_trident_autosupport
 
CWE
                
                    
                        
                        CWE-770
                        
            Allocation of Resources Without Limits or Throttling
