VDB

CVE-2022-21611

CVE-2022-21611 PUBLISHED CVSS 4.1 MEDIUM

Reported by oracle · Published October 18, 2022

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.30 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.1 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

Risk scores

CVSS 3.1
4.1
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H

Affected products

VendorProductVersions
Oracle CorporationMySQL Server8.0.30 and prior
chainguardmysql-8.00
Oracle CorporationMySQL Server8.0.30

Timeline

  • Oct 17, 2022 CVE Published
  • Oct 19, 2022 EPSS Score (30 in total, the first dated here)
  • Apr 3, 2026 Security Advisory (11 in total, the first dated here)
  • Jun 28, 2026 Distribution Patch (10 in total, the first dated here)
  • Jul 7, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2022-21611
vulnetix vdb fixes CVE-2022-21611

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-21611/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›