GHSA-F6PH-48M9-5R33
SQL injection in Buffer parameter escaping under big5: lead bytes 0xFA-0xFE are single bytes for the server
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 3.2.6 | mariadb · -7 d desde divulgación | |
| Remediación | Parche 3.3.5 | mariadb · -7 d desde divulgación | |
| Remediación | Parche 3.4.8 | mariadb · -7 d desde divulgación | |
| Remediación | Parche 3.5.5 | mariadb · -7 d desde divulgación | |
| Divulgación | Publicada | GHSA-F6PH-48M9-5R33 divulgada · CVSS 6.5 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
### Description
The charset-aware escaping of Buffer and stream parameters introduced for CVE-2026-55855 (GHSA-g5xc-5w98-jfvm) took big5 lead bytes as 0xA1 to 0xFE, while the server (strings/ctype-big5.c) and Connector/C stop at 0xF9. A Buffer starting with one of the five bytes 0xFA to 0xFE followed by 0x5C was copied verbatim, as a multibyte character, with no escape inserted before the 0x5C. The server reads that lead byte as a single byte and the 0x5C as an escape introducer, so a following quote ended the string literal and the rest of the value was parsed as SQL.
The text protocol is affected for Buffer and Readable stream parameters when the session charset is big5. Strings are covered by GHSA for CONJS-380. execute() and batch() are not affected: the binary protocol sends values out of band.
### Impact
An attacker controlling a Buffer or stream parameter of a text-protocol query, on a connection using the big5 client charset, could execute SQL inside the host statement with the privileges of the application's database user. With multipleStatements left to its default, the injection is bounded to the host statement: an unauthorized read in a SELECT, an unauthorized modification where the statement is DML.
Exposure requires the non-default big5 client charset, set through the charset or collation option, a connection string, or SET NAMES.
### Resolution
The big5 recognizer stops at 0xF9 like the server, so 0xFA to 0xFE are escaped as single bytes.
### Patches
Fixed in 3.2.6, 3.3.5, 3.4.8 and 3.5.5. Upgrade to the patched release of your branch.
### Workarounds
Use execute() or batch(), or use the default utf8mb4 client charset, until upgraded.
### References
CONJS-379: https://jira.mariadb.org/browse/CONJS-379
Fix commit: https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/c5702a9
### Credit
Reported by Yalguun Tumenkhuu (@fg0x0 https://github.com/fg0x0/).
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmmariadb |
Corregida | 3.2.6, 3.3.5, 3.4.8, 3.5.5 | -7 d · -7 d · -7 d · -7 d | 3.5.5 no afectada |
3.2.63.3.53.4.83.5.5Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-f6ph-48m9-5r33Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
