LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are 8.0.33 and prior. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 4.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let a highly privileged network user make an affected MySQL Server hang or crash repeatedly. It does not expose data or allow data changes in the cited CVSS assessment, but it can disrupt database availability.

Executive priority

Prioritize patching on business-critical databases and systems with remote privileged administration. This is not presented as actively exploited, but a repeatable database outage can still create material service impact.

Technical view

CVE-2023-22005 affects Oracle MySQL Server 8.0.33 and prior in the Server: Replication component. Oracle rates it CVSS 4.4 with network attack vector, high complexity, high privileges required, no user interaction, and availability-only impact causing complete denial of service.

Likely exposure

Exposure is mainly MySQL Server 8.0.33 and earlier where high-privileged users can reach the server over supported network protocols. Publicly exposed management or replication paths increase operational risk. Fedora and NetApp references indicate downstream distributions or products may need vendor-specific review.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Oracle describes exploitation as difficult and requiring high privileges. Treat this as an availability risk, not a confirmed data breach or remote unauthenticated compromise.

Researcher notes

The public description is limited to Oracle’s component, version range, privilege requirement, and denial-of-service impact. No CWE, proof-of-concept status, or detailed root cause is provided in the supplied sources, so validation should focus on version exposure and vendor patch state.

Mitigation direction

  • Apply Oracle’s July 2023 Critical Patch Update guidance for MySQL Server.
  • Upgrade affected MySQL Server 8.0.33 and prior deployments to a vendor-supported fixed release.
  • Review Fedora, NetApp, or appliance vendor advisories where MySQL is bundled.
  • Restrict network access to MySQL administration and replication interfaces.
  • Limit high-privileged MySQL accounts to trusted administrators and hosts.

Validation and detection

  • Inventory MySQL Server versions and flag 8.0.33 and earlier.
  • Identify systems using MySQL replication or high-privileged remote database access.
  • Confirm vendor patches or downstream package updates are installed.
  • Review database availability monitoring for unexplained hangs or repeated crashes.
  • Check whether affected MySQL is embedded in NetApp or distribution-managed products.
Prepared
Confidence
high
Sources
6

Public sources used

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-22005 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H0.73.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/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

Source materials

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.