Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ SUSE-SU-2023:2241-1 — mysql-connector-java (CVE-2023-21971)

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Security update for mysql-connector-java

This update for mysql-connector-java fixes the following issues:

  • CVE-2023-21971: Fixed a crash in MySQL Connectors that could be

triggered by an authenticated remote user (bsc#1211247).

  • Ship protobuf 3.9.2 compatible generated files to support

older distro versions.

  • Update to 8.0.32:
  • MysqlDataSource fails to URL encode database name when constructing JDBC URL.
  • serverSideStatementCache ignores resultSetType.
  • UpdatableResultSet does not properly handle unsigned primary key.
  • Connector/J 8 query with explain can not return ResultRow.
  • Add support to row alias on INSERT... ON DUPLICATE KEY UPDATE on batch mode.
  • connectionCollation ignored if characterEncoding is set.
  • Connector/J rejects UNION with CTE.
  • Malformed packet generation for COM_STMT_EXECUTE.
  • Connector/J client hangs after prepare & execute process with old version server.
  • Contribution: Fix name of relocation POM file.
  • Contribution: [PATCH] Remove superfluous use of boxing.
  • Contribution: Recognize 'ON DUPLICATE KEY UPDATE' in 'INSERT SET' Statement.
  • RPM and DEB builds broken after introducing javadoc for maven bundles.
  • Sonatype compliant POM and maven bundles.
  • Upgrade 3rd party libraries and tools.
  • Upgrade Protocol Buffers dependency to protobuf-java-3.21.9.
  • As Oracle renamed the package to 'mysql-connector-j', we are

'providing' both names for now, but the package has to be renamed

to accommodate the change because the old name will be deprecated

at some point in the future without further notice.

  • Update to 8.0.31:

Functionality Added or Changed

  • Important Change: To comply with proper naming guidelines, the

Maven groupId and artifactId for Connector/J have been changed

to the following starting with this release:

groupId: com.mysql

artifactId: mysql-connector-j

  • The old groupId and artifactId can still be used for linking

the Connector/J library, but they will point to a Maven

relocation POM, redirecting users to the new coordinates.

Please switch to the new coordinates as soon as possible, as

the old coordinates could be discontinued anytime without

notice. See Installing Connector/J Using Maven.

  • Also, to go with these changes, the .jar library for

Connector/J has been renamed to mysql-connector-j-x.y.z for

all channels of distribution by Oracle, not just the Maven

repository.

  • Before release 8.0.29, Connector/J always interpolated byte

arrays as hexadecimal literals when obtaining a prepared

statement's string representation by the toString() method.

Since 8.0.29, all byte array values were displayed as

BYTE ARRAY DATA when converted to strings. The same is

also true for null values.

  • To allow different ways to display byte array data and null

values, a new connection property, maxByteArrayAsHex, has been

introduced: byte arrays shorter than the value of

maxByteArrayAsHex are now shown as hexadecimal literals like

before release 8.0.29. Any byte arrays longer than this value

are interpolated generically as BYTE ARRAY DATA .

Bugs Fixed

  • X DevAPI: When parsing a string into a JSON string, some

escape character sequences were not parsed properly, causing

the Server to throw a com.mysql.cj.exceptions.WrongArgumentException

when receiving the JSON value. This fix ensures that escape

sequences are handled properly.

  • X DevAPI: When using the modify() method on JSON documents,

any backslashes inside a literal to be used for the modification

were lost. This fix corrects the mistakes in the expression

parser that caused the issue.

  • Executing a PreparedStatment after applying setFetchSize(0) on

it caused an ArrayIndexOutOfBoundsException.

  • Due to some old limitations, when used with Java applets,

Connector/J found out the default character set on a system by

various workarounds like reading the system property

file.encoding, using an OutpuStreamWriter, etc. With this fix,

Connector/J now uses Charset.defaultCharset(), the standard

method for the purpose.

  • Update to 8.0.30:

Functionality Added or Changed

  • X DevAPI: For document-modifying methods that are chained

after modify() and take a document path expression as one of

its arguments (that is, set(), unset(), arrayInsert(),

arrayAppend()), Connector/J now throws an error when the

document path is empty or is a null string.

Bugs Fixed

  • Historically, MySQL Server has used utf8 as an alias for

utf8mb3. Since release 8.0.29, utf8mb3 has become a recognized

(though deprecated) character set on its own for MySQL Server

and to make things consistent, in release 8.0.30, any

collations prefixed with utf8_ are now prefixe

Affected software

SUSE-SU-2023:2241-1 is recorded against 1 package.

  • mysql-connector-java (fixed in 8.0.32-150200.3.15.1)

Timeline and source

Published on 18 May 2023 and last revised on 2 May 2025. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

www.suse.com (Advisory)
bugzilla.suse.com (Report)
www.suse.com (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2023-05-18
Updated 2026-08-20
Modified 2025-05-02
Fix URL N/A

Affected Packages

Software From version Fixed in
mysql-connector-java 8.0.32-150200.3.15.1

Free Vulnerability Check

Is your site affected by SUSE-SU-2023:2241-1?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against SUSE-SU-2023:2241-1 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.