dbcve.org
Communications Cloud Native Core ConsoleApplication · Oracle

CVE-2021-2471

MEDIUM · 5.9 CVSS v3.1 Published 2021-10-20
Fix available
A fix is available. Upgrade to 2.2.4 / 2.6.0 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 Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.26 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 unauthorized access to critical data or complete access to all MySQL Connectors accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Connectors. CVSS 3.1 Base Score 5.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/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 Oracle MySQL Connector/J (component: Connector/J) affecting versions 8.0.26 and prior. Difficult to exploit flaw allows high privileged attackers with network access via multiple protocols to potentially gain unauthorized access to critical data or cause a complete denial of service (hang/frequent crashes).

MitigationUpgrade MySQL Connector/J to a version beyond 8.0.26 (when Oracle releases a patch) or apply Oracle's available security patches for this vulnerability. If immediate patching is not possible, restrict network access to Connector/J interfaces and limit privileged account usage.

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
Communications Cloud Native Core ConsoleApplication
Affected:= 1.9.0
Communications Cloud Native Core Network Slice Selection FunctionApplication
Affected:= 1.8.0
Communications Cloud Native Core PolicyApplication
Affected:= 1.15.0
Communications Cloud Native Core Security Edge Protection ProxyWeb browser
Affected:= 1.7.0
Mysql ConnectorsDatabase / datastore
Affected:>= 8.0.0, <= 8.0.26
QuarkusApplication
Affected:< 2.2.4>= 2.3.0, < 2.6.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
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/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 MySQL Connector/J version in use
    Inspect the application's dependency files (pom.xml for Maven, build.gradle for Gradle) or the mysql-connector-java.jar / mysql-connector-j.jar file version. Run: jar -xf mysql-connector-j.jar META-INF/MANIFEST.MF and check the Implementation-Version attribute.
    Affected if The Connector/J version is 8.0.26 or earlier, or falls within the 8.0.0 to 8.0.26 range.
  2. Check if application uses MySQL Connector/J
    Search the codebase for JDBC MySQL connection strings (jdbc:mysql://) and mysql-connector-java or mysql-connector-j imports in Java source files.
    Affected if The application establishes MySQL connections using the vulnerable Connector/J library.
  3. For Quarkus applications, verify Quarkus version
    Inspect pom.xml or build.gradle for the Quarkus version, or check the quarkus-core.jar MANIFEST.MF file.
    Affected if Quarkus version is less than 2.2.4, or between 2.3.0 and 2.6.0 (exclusive), which bundles vulnerable Connector/J.
  4. Identify Oracle Communications Cloud Native Core product versions
    Check the installed version of Oracle Communications Cloud Native Core Console (1.9.0), Network Slice Selection Function (1.8.0), Policy (1.15.0), or Security Edge Protection Proxy (1.7.0) by querying the product's about or version endpoint, or inspecting the installed package metadata.
    Affected if Any of these specific product versions are running (1.9.0, 1.8.0, 1.15.0, or 1.7.0 respectively).

You are affected if MySQL Connector/J version 8.0.26 or earlier is in use, or if running any of the listed Quarkus or Oracle Communications product versions that bundle the vulnerable connector.

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.2.4 / 2.6.0 or later
Fixed in 2.2.42.6.0
Interim mitigation

Upgrade MySQL Connector/J to a version beyond 8.0.26 (when Oracle releases a patch) or apply Oracle's available security patches for this vulnerability. If immediate patching is not possible, restrict network access to Connector/J interfaces and limit privileged account usage.

Recommended fix High confidence

MySQL Connector/J 8.0.27 or later

  1. 1. Identify the current MySQL Connector/J version in use by checking project dependencies or libraries
  2. 2. Download MySQL Connector/J version 8.0.27 or later from the official Oracle MySQL download page
  3. 3. Replace the existing mysql-connector-java or mysql-connector-j library in your project
  4. 4. Update dependency management (Maven pom.xml, Gradle build.gradle, or similar) to specify version 8.0.27 or later
  5. 5. Rebuild and redeploy the application
  6. 6. Verify the application functions correctly with the new connector version
Caveat Minimal risk - 8.0.27 was primarily a security patch; review release notes for any behavior changes if upgrading across multiple minor versions

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

Fix this in Communications Cloud Native Core Console Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
17.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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