Is mysql:mysql-connector-java 5.0 vulnerable?
Maven · 6 releases from 5.0.2 to 5.0.8 · latest mysql:mysql-connector-java is 8.0.33 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. mysql:mysql-connector-java 5.0.8, the last 5.0 release, is affected by 8 known security advisories (3 high, 4 medium, 1 low), including CVE-2023-22102, CVE-2018-3258, CVE-2017-3523. At least one has no fixed release yet.
Is your project on an affected mysql:mysql-connector-java?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting mysql:mysql-connector-java 5.0.8
MySQL Connectors takeover vulnerability
- Affected
- <=8.0.33
- Fixed in
- No fix released
Improper Access Control in MySQL Connectors Java
- Affected
- <5.1.35
- Fixed in
- 5.1.35
Improper Privilege Management in MySQL Connectors Java
- Affected
- <8.0.13
- Fixed in
- 8.0.13
Exposure of Sensitive Information to an Unauthorized Actor in Oracle MySQL Connectors Java
- Affected
- <5.1.42
- Fixed in
- 5.1.42
Exposure of Sensitive Information to an Unauthorized Actor in Oracle MySQL Connectors Java
- Affected
- <5.1.42
- Fixed in
- 5.1.42
Improper Access Control in MySQL Connectors Java
- Affected
- <5.1.41
- Fixed in
- 5.1.41
Improper Handling of Insufficient Permissions or Privileges in MySQL Connectors Java
- Affected
- <8.0.28
- Fixed in
- 8.0.28
Privilege escalation in mysql-connector-jav
- Affected
- <8.0.16
- Fixed in
- 8.0.16
Every mysql:mysql-connector-java 5.0.x release
Affected: 5.0.2 to 5.0.8. Latest mysql:mysql-connector-java: 8.0.33.
| Version | Known advisories |
|---|---|
| mysql:mysql-connector-java 5.0.8 | CVE-2023-22102, CVE-2015-2575, CVE-2018-3258, CVE-2017-3586, CVE-2017-3589, CVE-2017-3523, CVE-2022-21363, CVE-2019-2692 |
| mysql:mysql-connector-java 5.0.7 | CVE-2023-22102, CVE-2015-2575, CVE-2018-3258, CVE-2017-3586, CVE-2017-3589, CVE-2017-3523, CVE-2022-21363, CVE-2019-2692 |
| mysql:mysql-connector-java 5.0.5 | CVE-2023-22102, CVE-2015-2575, CVE-2018-3258, CVE-2017-3586, CVE-2017-3589, CVE-2017-3523, CVE-2022-21363, CVE-2019-2692 |
| mysql:mysql-connector-java 5.0.4 | CVE-2023-22102, CVE-2015-2575, CVE-2018-3258, CVE-2017-3586, CVE-2017-3589, CVE-2017-3523, CVE-2022-21363, CVE-2019-2692 |
| mysql:mysql-connector-java 5.0.3 | CVE-2023-22102, CVE-2015-2575, CVE-2018-3258, CVE-2017-3586, CVE-2017-3589, CVE-2017-3523, CVE-2022-21363, CVE-2019-2692 |
| mysql:mysql-connector-java 5.0.2 | CVE-2023-22102, CVE-2015-2575, CVE-2018-3258, CVE-2017-3586, CVE-2017-3589, CVE-2017-3523, CVE-2022-21363, CVE-2019-2692 |
Which of your client projects are still on mysql:mysql-connector-java 5.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact mysql:mysql-connector-java version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other mysql:mysql-connector-java versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.