dbcve.org
FedoraOperating system · Fedoraproject

CVE-2023-22053

MEDIUM · 5.9 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to after 8.0.32 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the MySQL Server product of Oracle MySQL (component: Client programs). Supported versions that are affected are 5.7.42 and prior and 8.0.33 and prior. Difficult to exploit vulnerability allows low 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 and unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vulnerability in MySQL Client programs (affecting versions 5.7.42 and prior, 8.0.33 and prior) allows a low-privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful exploitation enables a denial of service (server hang or crash) and unauthorized read access to a subset of accessible data.

MitigationUpgrade MySQL Server and client installations to versions beyond 5.7.42 and 8.0.33 respectively, as Oracle has addressed this vulnerability in subsequent patch updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 37= 38= 39
Mysql ServerDatabase / datastore
Affected:>= 5.0.0, <= 5.7.42>= 8.0.0, <= 8.0.32
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions
Oncommand Workflow AutomationApplication
Affected:all versions
SnapcenterApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MySQL Server version
    Run `mysql --version` or `mysqld --version` to retrieve the installed MySQL Server version number
    Affected if The version is 5.7.42 or lower, or between 8.0.0 and 8.0.32 inclusive
  2. Identify installed MySQL Client version
    Run `mysql --version` to check the client version separately from the server
    Affected if The client version is 5.7.42 or lower, or between 8.0.0 and 8.0.32 inclusive
  3. Check for NetApp Active IQ Unified Manager
    Verify presence of NetApp Active IQ Unified Manager installation using package manager or installed software list
    Affected if The software is present at any version (all versions are affected)
  4. Check for NetApp Oncommand Insight
    Verify presence of NetApp Oncommand Insight installation
    Affected if The software is present at any version (all versions are affected)
  5. Check for NetApp Oncommand Workflow Automation
    Verify presence of NetApp Oncommand Workflow Automation installation
    Affected if The software is present at any version (all versions are affected)
  6. Check for NetApp Snapcenter
    Verify presence of NetApp Snapcenter installation
    Affected if The software is present at any version (all versions are affected)

You are affected if you run MySQL Server or Client versions 5.7.42 or lower, or 8.0.32 or lower, or any version of the listed NetApp products.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.32
Interim mitigation

Upgrade MySQL Server and client installations to versions beyond 5.7.42 and 8.0.33 respectively, as Oracle has addressed this vulnerability in subsequent patch updates.

Recommended fix High confidence

MySQL Server 5.7.43+ or 8.0.34+; Fedora packages via dnf update

  1. 1. Identify the exact MySQL Server version currently installed using: `mysql --version` or `SELECT VERSION();`
  2. 2. For MySQL Server 5.7.x: Upgrade to MySQL Server 5.7.43 or later
  3. 3. For MySQL Server 8.0.x: Upgrade to MySQL Server 8.0.34 or later
  4. 4. On Fedora systems: Run `sudo dnf update mysql-server` to apply available security updates
  5. 5. After upgrade, verify the new version is running: `mysql --version`
  6. 6. Test application functionality to ensure compatibility with the new MySQL version
Caveat Minor version upgrades typically have low risk, but always test application compatibility before deploying to production. Review MySQL release notes for any behavioral changes between versions.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data