SIGSEGV (exit 134) in bundled `rightstr()` when the length argument is a large negative number

オープン
#1,508 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@sarthakdev143-lite がすでに取り組んでいます。

2026年11月14日 から。

  • #1509 @sarthakdev143-lite による — オープン

評価

難易度
4/5
見積もり時間
1〜2日
初心者へのやさしさ
38/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
c, java, sqlite
領域
database

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

help wanted impacts:JNI

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.

主要言語
Java
スター
3.3k
フォーク
676
平均マージ
1日 15時間
マージ済み PR(30日)
18

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

xerial/sqlite-jdbc のほかの issue

xerial/sqlite-jdbc の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。