How severe is CVE-2018-3258?

CVE-2018-3258 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-3258?

CVE-2018-3258 affects the following packages: mysql:mysql-connector-java (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-3258?

Update mysql:mysql-connector-java to 8.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-3258 is resolved across your whole dependency graph.

How do I detect CVE-2018-3258 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql:mysql-connector-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-3258 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-3258 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-3258 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-3258?

CVE-2018-3258 has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2018-3258 published, and has it been updated?

CVE-2018-3258 was published on May 13, 2022 and was last updated on February 20, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2018-3258 — mysql-connector-java

HIGH

CVE-2018-3258 is a high-severity (CVSS 8.8) vulnerability in mysql:mysql-connector-java. A fix is available for mysql:mysql-connector-java — see the affected versions and patch details below.

Improper Privilege Management in MySQL Connectors Java

Published

May 13, 2022

Updated

Feb 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2018-3258.

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕mysql:mysql-connector-java

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.12 and prior. Easily exploitable vulnerability allows low 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.0 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`mysql:mysql-connector-java`	all versions	8.0.13`mysql:mysql-connector-java:8.0.13`

Affected Products

1 product · 1 configurations

Application

connector\/joracle

≤ 8.0.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql:mysql-connector-java, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mysql:mysql-connector-java to 8.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-3258 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Re Hat Satellite does not support using mysql as a back end database, thus the mysql connector is not used in any Satellite installation. The package mariadb Java client is now available in Red Hat Software Collections. It can be installed this way: ~~~ yum-config-manager --enable rhel-server-rhscl-7-rpms yum install…

Product	Fixed in	Advisory
Red Hat Fuse 7.3.1	`mysql-connector-java`	RHSA-2019:1545
Red Hat Satellite 6.8 for RHEL 7	`ansible-collection-redhat-satellite-0:1.3.0-1.el7sat`	RHSA-2020:4366

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-3258 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 13, 2022

Last updated

Feb 20, 2024

Identifiers

CVE-2018-3258

References

Advisorynvd.nist.gov · CVE 2018 3258 Webaccess.redhat.com · RHSA 2019:1545 Websecurity.netapp.com · ntap 20181018 0002 Weboracle.com · cpuoct2018 4428296

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs affecting mysql-connector-java are rated as high or higher (top: high).

CVE-2023-22102CVE-2021-2471CVE-2015-2575CVE-2017-3523CVE-2017-3589CVE-2017-3586CVE-2022-21363CVE-2019-2692

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 20, 2024

CVE-2018-3258 — mysql-connector-java

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2018-3258 in your dependencies?