LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22008: Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.33 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols 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.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-22008 is a denial-of-service issue in Oracle MySQL Server's InnoDB component. A highly privileged user who can reach the server over the network could cause MySQL to hang or crash repeatedly. The business impact is service availability, not data theft or modification based on the supplied sources.

Executive priority

Treat this as a moderate-priority availability risk. It should be patched through normal security maintenance, faster for production databases where outages affect revenue, customer operations, or service commitments. The supplied evidence does not indicate data compromise or active exploitation.

Technical view

Oracle reports affected MySQL Server versions as 8.0.33 and prior. CVSS 3.1 is 4.9 with network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high availability impact only. No CWE is provided in the bundle.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.33 or earlier is reachable by privileged database users over network-accessible protocols. Internet exposure matters less than credentialed administrative or high-privilege access paths. Downstream NetApp and Fedora references indicate packaged environments may also need vendor-specific checks.

Exploitation context

The provided bundle does not show CISA KEV listing or cite active exploitation. The vulnerability is described as easily exploitable, but only by a high-privileged attacker with network access. Expected impact is a hang or frequently repeatable crash causing complete denial of service.

Researcher notes

Key constraints are high privileges and availability-only impact. The affected component is InnoDB, but the bundle does not provide root cause, CWE, exploit details, or exact fixed version. Avoid assuming exploit maturity; validate exposure through version, packaging source, reachable protocols, and privileged account paths.

Mitigation direction

  • Apply Oracle's July 2023 Critical Patch Update guidance for affected MySQL Server deployments.
  • Update MySQL Server packages from the relevant downstream vendor, such as Fedora or NetApp where applicable.
  • Restrict network access to MySQL services to trusted administrative and application paths only.
  • Review and reduce high-privilege MySQL accounts that are unnecessary for operations.
  • If patch details are unclear, verify current remediation guidance with the product vendor.

Validation and detection

  • Inventory MySQL Server instances and identify versions 8.0.33 and earlier.
  • Confirm whether each instance uses Oracle, Fedora, NetApp, or another vendor distribution.
  • Verify installed package or server build against the applicable vendor advisory.
  • Review MySQL availability logs for unexplained hangs or repeated crash patterns.
  • Confirm high-privilege database accounts are limited and monitored.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-22008 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2023-22008Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Server*Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.