dbcve.org
Mysql ConnectorsDatabase / datastore · Oracle

CVE-2022-21363

MEDIUM · 6.6 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to 2.7.0 or later.
See remediation →
72/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 Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/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 Oracle MySQL Connector/J (JDBC driver) versions 8.0.27 and prior. Difficult to exploit vulnerability requiring high-privileged attacker with network access can lead to complete takeover of MySQL Connectors.

MitigationUpdate MySQL Connector/J to a version beyond 8.0.27 (refer to Oracle Critical Patch Updates for patched version). Alternatively, restrict network access and ensure only trusted high-privileged users can interact with the connector.

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
Mysql ConnectorsDatabase / datastore
Affected:>= 8.0.0, <= 8.0.27
QuarkusApplication
Affected:< 2.7.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/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 MySQL Connector/J version
    Locate the mysql-connector-java.jar or mysql-connector-j.jar file in your application classpath or lib directory. Check the manifest file inside the JAR or examine the dependency declaration in your build configuration (pom.xml for Maven, build.gradle for Gradle).
    Affected if The reported version is greater than or equal to 8.0.0 and less than or equal to 8.0.27
  2. Check if Quarkus is used
    Examine your project dependencies for Quarkus core libraries (quarkus-core, quarkus-arc, etc.) or check your pom.xml/build.gradle for Quarkus dependencies.
    Affected if Quarkus version is less than 2.7.0 and it bundles MySQL Connector/J for database connectivity
  3. Verify network exposure of the connector
    Review your network configuration and firewall rules to determine if the MySQL Connector/J endpoint is accessible from untrusted networks. Check if the application listens on protected or internal-only network interfaces.
    Affected if The connector is exposed to network access from untrusted sources, increasing exploitability
  4. Assess attacker privilege requirements
    Review user accounts and access controls for the MySQL database and application layer. Determine if low-privileged or anonymous users can interact with the connector.
    Affected if The application permits high-privileged database user accounts with network access to connect through the JDBC driver

You are affected if your environment uses MySQL Connector/J version 8.0.0 through 8.0.27, or Quarkus below 2.7.0 with MySQL connectivity, and the connector is accessible to high-privileged attackers over the network.

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 2.7.0 or later
Fixed in 2.7.0
Interim mitigation

Update MySQL Connector/J to a version beyond 8.0.27 (refer to Oracle Critical Patch Updates for patched version). Alternatively, restrict network access and ensure only trusted high-privileged users can interact with the connector.

Recommended fix High confidence

MySQL Connector/J: 8.0.28 or later; Quarkus: 2.7.0 or later

  1. 1. For MySQL Connector/J: Upgrade to version 8.0.28 or later (the next stable release after 8.0.27 that contains the security fix).
  2. 2. Update the Maven dependency in pom.xml: Change mysql-connector-java version to 8.0.28 or later, or use mysql-connector-j which is the new package name.
  3. 3. If using Quarkus: Upgrade Quarkus to version 2.7.0 or later to receive the bundled fixed Connector/J.
  4. 4. Rebuild and redeploy the application with the updated dependency.
  5. 5. Verify the application functions correctly with the new connector version.
Caveat Minor - Connector/J 8.0.28 includes security fixes with no expected breaking changes; verify any deprecated API usage

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

Fix this in Mysql Connectors Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing8.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21363 — 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-2022-21363 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