hyper-rustls 0.25 pin transitively forces rustls-webpki 0.102.x, which has unpatchable advisories (incl. one high)
维护者通常 11 天内回复
还没有人认领这个 Issue。
评估
调研方向
从 libsql/Cargo.toml 中 hyper 依赖附近开始,跟踪远程/同步 HTTP 客户端和默认 tls 特性。比较提出的三种路径:迁移到 hyper 1.x、直接使用 rustls 0.23 connector,或让 tls 采用 opt-in。完成的标准是移除或避开无法解析的 rustls-webpki 依赖,并记录默认特性的兼容性影响。
由索引模型根据 Issue 内容生成。
描述
Summary
libsql's tls feature (which is on by default) pins hyper-rustls = "0.25". That version line only ever depended on rustls 0.22, which in turn requires rustls-webpki ^0.102. Because 0.102.8 is the last release in the 0.102 line, and the relevant fixes only landed in 0.103.10 / 0.103.12 / 0.103.13, every downstream consumer of libsql inherits four rustls-webpki advisories with no reachable fix.
The chain
libsql 0.9.30 (tls, default)
-> hyper-rustls 0.25.0 (only 0.25.x release)
-> rustls 0.22.4 (last 0.22.x release)
-> rustls-webpki ^0.102 -> 0.102.8 (last 0.102.x release)
Every link is already at its ceiling, so no cargo update can resolve this.
Advisories inherited
| Advisory | Severity | Fixed in |
|---|---|---|
| GHSA-82j2-j2ch-gfr8 — DoS via panic on malformed CRL BIT STRING | high (CVSS 7.5) | 0.103.13 |
| GHSA-pwjx-qhcg-rvj4 — CRLs not authoritative by Distribution Point | medium | 0.103.10 |
| GHSA-965h-392x-2mh5 — URI name constraints incorrectly accepted | low | 0.103.12 |
| GHSA-xgp8-3hg3-c2mh — name constraints accepted for wildcard certs | low | 0.103.12 |
To be clear about impact: we assessed the two CRL ones as not reachable through libsql, since rustls only parses CRLs when they're explicitly supplied via with_crls(), and neither libsql nor hyper-rustls 0.25 ever does. So this is primarily a dependency-hygiene / compliance problem rather than an exploitable one — but it still surfaces as an unresolvable high-severity Dependabot alert in every downstream repo, which is painful for anyone under SOC2-style "no open highs" policies. We ended up having to dismiss them with written justification.
Why it isn't a one-line bump
hyper-rustls moved to rustls 0.23 (and thus webpki 0.103) in 0.26, but 0.26+ also requires hyper 1.x. libsql is still on hyper = "0.14":
https://github.com/tursodatabase/libsql/blob/main/libsql/Cargo.toml#L20-L21
So closing this properly means a hyper 0.14 → 1.x migration for the remote/sync HTTP client. Confirmed still present on main, and on 0.10.0-pre.4.
Possible options, roughly in order of effort
- Migrate to hyper 1.x + hyper-rustls 0.27. The real fix; also unblocks a lot of other modernization.
- Swap the TLS stack for
rustls0.23 directly behind libsql's own connector, decoupling from hyper-rustls' hyper requirement. - Interim mitigation — drop
tlsfromdefault. Consumers that only use local databases (Builder::new_local) currently pull the whole rustls 0.22 stack for nothing. Notablytlsis already independent:remote,sync, andreplicationdo not depend on it, so making it opt-in would be a small change that lets local-only users escape these advisories entirely. It is technically a breaking change for anyone relying on defaults for remote TLS, so it'd want a minor-version note.
Happy to put up a PR for (3) if that's a direction you'd accept — it's the one that would unblock downstream consumers soonest. (1) looks like it needs a maintainer to scope.
Environment
- libsql 0.9.30 (also verified against
mainand0.10.0-pre.4) - Discovered via Dependabot on a downstream Rust project that uses libsql only through
Builder::new_local
- 主要语言
- C
- 星标
- 17.3k
- 派生
- 562
- 平均合并
- 10 天 15 小时
- 30 天内合并 PR
- 1
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
tursodatabase/libsql 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
tursodatabase/libsql#2320 ·
维护者通常 11 天内回复
-
`cloudflare` feature: hrana streams are never closed可能已有人在做 @pcbeingused333 于 4 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
tursodatabase/libsql#2312 ·
维护者通常 11 天内回复
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batch可能已有人在做 @pavanmanishd 于 25 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 83/100
tursodatabase/libsql#2298 · 1 条评论 ·
维护者通常 11 天内回复
-
Rust local Row::get_value truncates embedded NUL TEXT and panics on malformed UTF-8 (0.9.30)可能已有人在做 @Sanjays2402 于 35 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
tursodatabase/libsql#2285 ·
维护者通常 11 天内回复
-
libsql-ffi: broken builds under Nix on macOS可能已有人在做 @frectonz 于 85 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
tursodatabase/libsql#2275 ·
维护者通常 11 天内回复
查看 tursodatabase/libsql 的全部 Issue
相似的 Issue
-
Event areas未关闭layer:flagship m5 slice topic:World & Travel
难度 2/5 1-3 小时 新手友好度 65/100
Life-Framework/Life-Framework#2243 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100