CVE-2022-21322 json
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General).
published 4y ago modified 4mo ago also EUVD-2022-26547
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
Patch / fix
- oracle mysql_cluster 8.0.28
Is CVE-2022-21322 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
2.62% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.0 | AV:A/AC:H/Au:S/C:P/I:P/A:P |
Affected products
- Oracle Corporation MySQL Cluster
References
-
oracle.com
/security-alerts/cpujan2022.html
vendor-advisory
-
security.netapp.com
/advisory/ntap-20220121-0008/
third-party-advisory
-
zerodayinitiative.com
/advisories/ZDI-22-107/
third-party-advisory
Sources
- CVE List CVE-2022-21322
- NVD CVE-2022-21322
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Improve version ranges to indicate fix.