mariadb 2.0.3

Direct Vulnerabilities

Known vulnerabilities in the mariadb package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H SQL Injection Affected versions of this package are vulnerable to SQL Injection via the text protocol escape logic in `lib/io/packet-output-stream.js` when the server session has the `NO_BACKSLASH_ESCAPES` mode enabled. In that mode, backslash is an ordinary character, so escaping a single quote with a backslash leaves the quote intact and closes the string literal, allowing an attacker to inject arbitrary SQL through user-supplied string values. Note: This is only exploitable when the MariaDB server session uses the `NO_BACKSLASH_ESCAPES` SQL mode. How to fix SQL Injection? Upgrade `mariadb` to version 3.2.5, 3.3.4, 3.4.7, 3.5.4 or higher.	<3.2.5>=3.3.0 <3.3.4>=3.4.0 <3.4.7>=3.5.1 <3.5.4
H Use of Uninitialized Resource Affected versions of this package are vulnerable to Use of Uninitialized Resource via the GeoJSON Polygon and MultiPolygon encoding path in `lib/cmd/encoder/binary-encoder.js` when a ring element within the `coordinates` array is not a real array. The encoder sizes the output buffer using `Buffer.allocUnsafe` based on each ring's `length` property, then writes coordinate data only when the ring passes an `Array.isArray` check. When a non-array ring is supplied, the writing loop is skipped while the allocated bytes remain uninitialized, causing process heap memory to be transmitted to the database server in the binary protocol packet. An attacker who can supply GeoJSON Polygon or MultiPolygon query parameters can leak arbitrary Node.js process memory to the server. How to fix Use of Uninitialized Resource? Upgrade `mariadb` to version 3.2.5, 3.3.4, 3.4.7, 3.5.4 or higher.	<3.2.5>=3.3.0 <3.3.4>=3.4.0 <3.4.7>=3.5.1 <3.5.4
M Insufficiently Protected Credentials Affected versions of this package are vulnerable to Insufficiently Protected Credentials via the `SendPamAuthPacketFactory` function. An attacker can intercept sensitive credentials by performing a man-in-the-middle attack or controlling a malicious server that issues an Authentication Switch Request for the dialog plugin over an insecure connection. Note: This is only exploitable if connections occur over plain TCP (`sslMode'='DISABLE') or a TLS mode that only verifies server identity via self-signed-certificate fingerprint validation, and the attacker can occupy an on-path position or control the server. How to fix Insufficiently Protected Credentials? Upgrade `mariadb` to version 3.5.3 or higher.	<3.5.3
H Improper Encoding or Escaping of Output Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output in the client-side escaping of Buffer parameters under certain multi-byte client character sets, specifically `big5`, `gbk`, `sjis`, `cp932`, or `gb18030`. An attacker can gain unauthorized access to or modify data by supplying crafted input that manipulates the escaping process, causing the intended string literal to be terminated and arbitrary SQL to be executed. Note: This is only exploitable if the connection's client character set is set to one of the affected multi-byte charsets and untrusted data is bound as a Buffer parameter. How to fix Improper Encoding or Escaping of Output? Upgrade `mariadb` to version 3.5.3 or higher.	<3.5.3
H Insufficiently Protected Credentials Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the authentication. An attacker can intercept sensitive credentials by performing a man-in-the-middle attack during the initial handshake. Note: This is only exploitable if `SSL/TLS` is enabled without providing a CA or server certificate and the connection relies solely on fingerprint validation. How to fix Insufficiently Protected Credentials? Upgrade `mariadb` to version 3.5.3 or higher.	<3.5.3

Vulnerability

Vulnerable Version

SQL Injection

Affected versions of this package are vulnerable to SQL Injection via the text protocol escape logic in lib/io/packet-output-stream.js when the server session has the NO_BACKSLASH_ESCAPES mode enabled. In that mode, backslash is an ordinary character, so escaping a single quote with a backslash leaves the quote intact and closes the string literal, allowing an attacker to inject arbitrary SQL through user-supplied string values.

Note: This is only exploitable when the MariaDB server session uses the NO_BACKSLASH_ESCAPES SQL mode.

How to fix SQL Injection?

Upgrade mariadb to version 3.2.5, 3.3.4, 3.4.7, 3.5.4 or higher.

<3.2.5>=3.3.0 <3.3.4>=3.4.0 <3.4.7>=3.5.1 <3.5.4

Use of Uninitialized Resource

Affected versions of this package are vulnerable to Use of Uninitialized Resource via the GeoJSON Polygon and MultiPolygon encoding path in lib/cmd/encoder/binary-encoder.js when a ring element within the coordinates array is not a real array. The encoder sizes the output buffer using Buffer.allocUnsafe based on each ring's length property, then writes coordinate data only when the ring passes an Array.isArray check. When a non-array ring is supplied, the writing loop is skipped while the allocated bytes remain uninitialized, causing process heap memory to be transmitted to the database server in the binary protocol packet. An attacker who can supply GeoJSON Polygon or MultiPolygon query parameters can leak arbitrary Node.js process memory to the server.

How to fix Use of Uninitialized Resource?

Upgrade mariadb to version 3.2.5, 3.3.4, 3.4.7, 3.5.4 or higher.

<3.2.5>=3.3.0 <3.3.4>=3.4.0 <3.4.7>=3.5.1 <3.5.4

Insufficiently Protected Credentials

Affected versions of this package are vulnerable to Insufficiently Protected Credentials via the SendPamAuthPacketFactory function. An attacker can intercept sensitive credentials by performing a man-in-the-middle attack or controlling a malicious server that issues an Authentication Switch Request for the dialog plugin over an insecure connection.

Note: This is only exploitable if connections occur over plain TCP (`sslMode'='DISABLE') or a TLS mode that only verifies server identity via self-signed-certificate fingerprint validation, and the attacker can occupy an on-path position or control the server.

How to fix Insufficiently Protected Credentials?

Upgrade mariadb to version 3.5.3 or higher.

<3.5.3

Improper Encoding or Escaping of Output

Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output in the client-side escaping of Buffer parameters under certain multi-byte client character sets, specifically big5, gbk, sjis, cp932, or gb18030. An attacker can gain unauthorized access to or modify data by supplying crafted input that manipulates the escaping process, causing the intended string literal to be terminated and arbitrary SQL to be executed.

Note: This is only exploitable if the connection's client character set is set to one of the affected multi-byte charsets and untrusted data is bound as a Buffer parameter.

How to fix Improper Encoding or Escaping of Output?

Upgrade mariadb to version 3.5.3 or higher.

<3.5.3

Insufficiently Protected Credentials

Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the authentication. An attacker can intercept sensitive credentials by performing a man-in-the-middle attack during the initial handshake.

Note: This is only exploitable if SSL/TLS is enabled without providing a CA or server certificate and the connection relies solely on fingerprint validation.

How to fix Insufficiently Protected Credentials?

Upgrade mariadb to version 3.5.3 or higher.

<3.5.3

mariadb@2.0.3

fast mariadb or mysql connector.

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically