SB2023081405 - Multiple vulnerabiltiies in Red Hat OpenShift Service Mesh Containers 2.3
Published: August 14, 2023
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 6 secuirty vulnerabilities.
1) Improper Encoding or Escaping of Output (CVE-ID: CVE-2023-35941)
The vulnerability allows a remote attacker to compromise the target system.
The vulnerability exists due to improper encoding or escaping of output. A remote attacker can construct credentials with permanent validity.
2) Use-after-free (CVE-ID: CVE-2023-35942)
The vulnerability allows a remote attacker to compromise vulnerable system.
The vulnerability exists due to a use-after-free error in the gRPC access logger extension. A remote user can perform a denial of service (DoS) attack.
3) Use-after-free (CVE-ID: CVE-2023-35943)
The vulnerability allows a remote attacker to compromise vulnerable system.
The vulnerability exists due to a use-after-free error in the HTTP CORS filter. A remote user can perform a denial of service (DoS) attack.
4) Input validation error (CVE-ID: CVE-2023-35944)
The vulnerability allows a remote attacker to compromise the target system.
The vulnerability exists due to incorrect handling of requests and responses with mixed case schemes. A remote attacker can pass specially crafted input to the application and bypass some requests with mixed schemes.
5) Memory leak (CVE-ID: CVE-2023-35945)
The vulnerability allows a remote attacker to perform DoS attack on the target system.
The vulnerability exists due memory leak when handling HTTP/2 requests within the nghttp2 codec. A remote attacker can send RST_STREAM immediately followed by the GOAWAY frames to the application and force memory leak.
6) Resource exhaustion (CVE-ID: CVE-2023-2828)
The vulnerability allows a remote attacker to perform a denial of service (DoS) attack.
The vulnerability exists due to application does not properly control consumption of internal resources. A remote attacker can cause the amount of memory used by a named resolver to go well beyond the configured max-cache-size limit. The effectiveness of the attack depends on a number of factors (e.g. query load, query patterns), but since the default value of the max-cache-size statement is 90%, in the worst case the attacker can exhaust all available memory on the host running named, leading to a denial-of-service condition.
Remediation
Install update from vendor's website.