CVE-2026-101771
개요
A flaw was found in the Client programs component of MySQL. This issue may allow an attacker to impact the confidentiality, integrity, and/or availability of MySQL Server depending on the vulnerability details. Refer to the Oracle CPU advisory for component-specific impact.
내용
This vulnerability is rated as Important severity because an unauthenticated remote attacker could compromise the database service to achieve complete takeover, causing total loss of confidentiality, integrity, and availability. The impact is categorized as Important rather than Critical due to the high attack complexity and specific conditions necessary to successfully exploit the flaw. In standard Red Hat Enterprise Linux environments, database services are routinely isolated within protected internal subnets or restricted to local communication, which significantly limits exposure to untrusted network traffic.
CVSS (Common Vulnerability Scoring System) 점수 세부 사항
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
다음의 CVSS 지표 및 점수는 예비 정보로 검토 대상입니다.
CVSS v3 점수 분석
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| 기본 점수 | 8.1 | N/A | 8.1 |
| 공격 벡터 | Network | N/A | Network |
| 공격 복잡성 | High | N/A | High |
| 필요한 권한 | None | N/A | None |
| 사용자 상호 작용 | None | N/A | None |
| 범위 | Unchanged | N/A | Unchanged |
| 기밀성 | High | N/A | High |
| 무결성에 미치는 영향 | High | N/A | High |
| 가용성에 미치는 영향 | High | N/A | High |
벡터
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
취약점 이해 (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.