Skip to content
Fencer Intel
medium 4.9

CVE-2015-2575 json

Improper Access Control in MySQL Connectors Java

published 2015-04-16 11 y ago modified 2026-06-17 4 mo ago also GHSA-gc43-g62c-99g2 , EUVD-2022-3934

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.6%
EPSS 3.6% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

Unspecified vulnerability in the MySQL Connectors component in Oracle MySQL 5.1.34 and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Connector/J.

Patch / fix

  • maven mysql:mysql-connector-java 5.1.35
  • mysql-connector-java SLE Software Development Kit 12 SP1 5.1.35-3.1

suse advisories SUSE-SU-2016:2259-1

  • mysql-connector-java openSUSE Tumbleweed 5.1.35-2.3

opensuse advisories openSUSE-SU-2024:10286-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-2575 updated cvss 4.9

mysql-connector-java: unspecified vulnerability related to Connector/J (CPU April 2015)

  • Red Hat Enterprise Linux 6 mysql-connector-java Red Hat Enterprise Linux 7 mysql-connector-java
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse Service Works 6 mysql-connector-java Red Hat JBoss Portal 6 mysql-connector-java Red Hat OpenShift Enterprise 2 mysql-connector-java
    affected: no fix available
  • Red Hat JBoss Data Grid 6 mysql-connector-java
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.56% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.9 AV:N/AC:M/Au:S/C:P/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven mysql:mysql-connector-java
<5.1.35
5.1.35

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.