SIGSEGV (exit 134) in bundled `rightstr()` when the length argument is a large negative number
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 38/100
Direzione di ricerca
Start by reproducing with the one-line SELECT rightstr('abcdef', -1000000000) through the JDBC driver, then find rightstr in the bundled contrib extension-functions.c, focusing on the negative-length branch. The fix belongs in that C code, which the native library build compiles, so you will need to build libsqlitejdbc locally. Done means a large negative length returns an empty string or a clean error with no SIGSEGV, while small negatives still behave as before.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Describe the bug
A single SELECT rightstr(<text>, <large negative>) kills the whole JVM process with SIGSEGV — no Java exception can catch it, no SQLITE_NOMEM is returned, the process just dies (exit code 134).
rightstr is not a core SQLite function; it is supplied by the extension-functions code compiled into the native library shipped in this jar (libsqlitejdbc.dylib). Only the negative length branch of rightstr crashes: small negatives return an empty string, magnitudes ≥ ~2e8 segfault. Positive lengths of the same magnitude and leftstr with the same argument stay clean.
To Reproduce
SELECT rightstr('abcdef', -1000000000);
Connection c = DriverManager.getConnection("jdbc:sqlite::memory:");
try (ResultSet r = c.createStatement()
.executeQuery("SELECT rightstr('abcdef', -1000000000)")) {
while (r.next()) { }
}
java -cp "sqlite-jdbc-<version>.jar:." Repro
echo $? # 134
Expected behavior
Same as small negative arguments: an empty string (rightstr('abcdef', -1) returns length 0). At worst a clean error such as SQLITE_NOMEM / SQLITE_TOOBIG, as happens for positive lengths and for replicate('abcdef', 2147483647).
Logs
JVM crash report (hs_err_pid*.log):
# SIGSEGV (0xb) at pc=0x0000000104045a74
# Problematic frame:
# C [sqlite-3.54.1.0-...-libsqlitejdbc.dylib+0x1da74]
Native frames:
C libsqlitejdbc.dylib+0x1da74
C libsqlitejdbc.dylib+0x34e70
C libsqlitejdbc.dylib+0xbebc
J org.sqlite.core.NativeDB.step(J)I
J org.sqlite.core.DB.execute(J[Ljava/lang/Object;)I
J org.sqlite.core.JDBC3Statement.executeQuery
The crash happens inside SQLite expression evaluation (step), not in the JDBC wrapper.
Environment (please complete the following information)
- OS: macOS 15.6.1 (24G90)
- CPU architecture: arm64
- sqlite-jdbc version: 3.54.1.0 (bundled SQLite 3.54.1), JDK 25.0.1+8
Additional context
Stability — one fresh JVM per run, same single statement:
| length argument | result |
|---|---|
| -1e6 / -1e7 / -5e7 / -1e8 | no crash |
| -2e8 | 2/8 crash |
| -3e8 | 7/8 crash |
| -5e8 / -8e8 / -1e9 / -1.5e9 / -2e9 | 8/8 crash |
| INT64_MIN (-9223372036854775808) | 0/2 crash |
Reproduced across driver versions with -1000000000 (3 runs each): 3.49.1.0 → 3/3, 3.51.2.0 → 3/3, 3.53.4.0 → 3/3, 3.54.1.0 → 3/3.
Control group, same magnitude, no crash:
| statement | result |
|---|---|
leftstr('abcdef', -1000000000) |
0/5 |
substr('abcdef', -200000000) |
0/3 |
rightstr('abcdef', 200000000) |
0/3 |
padl('abcdef', 200000000, 'x') |
0/3 |
padr('abcdef', 200000000, 'x') |
0/3 |
padc('abcdef', 2000000000) |
0/5 |
replicate('abcdef', 2147483647) |
clean SQLITE_NOMEM: a malloc() failed |
Since positive lengths of the same size only produce a clean SQLITE_NOMEM/SQLITE_TOOBIG, this is not memory exhaustion: the length/pointer computation on the negative branch goes out of bounds once |N| reaches roughly 2e8.
Suggested fix: handle N < 0 explicitly in rightstr (return an empty string or sqlite3_result_error), and check nByte > db->aLimit[SQLITE_LIMIT_LENGTH] before allocating, as core substr does.
rightstr is not core SQLite — it comes from contrib extension-functions.c, which SQLite itself does not maintain. The crash is inside libsqlitejdbc.dylib, which this project compiles and ships, hence the report here. Found by sqlancer PST mutation testing while probing function parameter domains.
- Lingua principale
- Java
- Stelle
- 3.3k
- Fork
- 676
- Merge medio
- 1g 15h
- PR unite (30g)
- 18
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di xerial/sqlite-jdbc
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
xerial/sqlite-jdbc#1515 ·
I maintainer di solito rispondono entro 1 giorno
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
xerial/sqlite-jdbc#1514 ·
I maintainer di solito rispondono entro 1 giorno
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
xerial/sqlite-jdbc#1513 ·
I maintainer di solito rispondono entro 1 giorno
-
triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
xerial/sqlite-jdbc#1512 ·
I maintainer di solito rispondono entro 1 giorno
-
triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
xerial/sqlite-jdbc#1483 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di xerial/sqlite-jdbc
Issue simili
-
Area/Configuration Type/Improvement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
ballerina-platform/static-code-analysis-tool#217 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
eclipse-dirigible/dirigible#8636 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug severity-medium XS
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
nikolas-charalambidis/facepalm-maven-plugin#291 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
OakLoaf/PluginUpdater#264 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: withStartupTimeout() changes the startup timeout of all containers that use the default wait strategyForse già presa @aymenjamaaoui l’ha presa oggi. Apertatype/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
testcontainers/testcontainers-java#12171 ·
I maintainer di solito rispondono entro 1 giorno