Dasel: Selector lexer panics on trailing whitespace in `parseCurRune`GHSA-65gg-g7rw-6cpc
MEDIUMFix: TomWright/dasel@eee03aeGHSA-65gg-g7rw-6cpc is a medium-severity (CVSS 6.2) CWE-129 vulnerability in github.com/tomwright/dasel/v3. A fix is available for github.com/tomwright/dasel/v3 — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-65gg-g7rw-6cpc.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-65gg-g7rw-6cpc by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/tomwright/dasel/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Same panic class as GHSA-m5j3-4634-c2vq and GHSA-m6xr-fvfg-5g64, sister site on the same function. Trigger is any selector ending in whitespace: dasel query 'a ' panics at selector/lexer/tokenize.go:60.
The whitespace-skip loop right above (lines 55-57) advances p.i to p.srcLen when the input is all-whitespace or whitespace-trailing. The very next line reads p.src[p.i] without a bounds check.
Vulnerable code
selector/lexer/tokenize.go:53-74 (v3.11.0):
func (p *Tokenizer) parseCurRune() (Token, error) {
// Skip over whitespace
for p.i < p.srcLen && unicode.IsSpace(rune(p.src[p.i])) {
p.i++
}
// Skip over comments
if p.src[p.i] == '/' && p.i+1 < p.srcLen && p.src[p.i+1] == '/' {
// ...
Lines 69-71 right below already do the bounds check after the comment-skip path. The whitespace-only path slipped past it.
Reproduce
$ echo '{"a":1}' | dasel query -i json 'a '
panic: runtime error: index out of range [2] with length 2
goroutine 1 [running]:
github.com/tomwright/dasel/v3/selector/lexer.(*Tokenizer).parseCurRune(...)
selector/lexer/tokenize.go:60
github.com/tomwright/dasel/v3/selector/lexer.(*Tokenizer).Next(...)
github.com/tomwright/dasel/v3/selector/lexer.(*Tokenizer).Tokenize(...)
github.com/tomwright/dasel/v3/selector.Parse(...)
github.com/tomwright/dasel/v3/execution.ExecuteSelector(...)
Other inputs that hit it: ' ', $'a\t', $'a\n', 'a ?? ', 'a + '. Any token (or no token) followed by whitespace.
Reachable directly from the library too - dasel.Query(ctx, input, "a ") panics the same way. Project-style test reproducer that fails on current main:
// drop into selector/lexer/ as tokenize_trailing_ws_test.go
package lexer_test
import (
"testing"
"github.com/tomwright/dasel/v3/selector/lexer"
)
func TestTokenize_TrailingWhitespacePanic(t *testing.T) {
defer func() {
if r := recover(); r != nil {
t.Fatalf("Tokenize panicked: %v", r)
}
}()
_, _ = lexer.NewTokenizer("a ").Tokenize()
}
Impact
Process crash, no auth, no preconditions. Same severity tier as the two May 13 advisories on this file.
Affected versions
All v3.x. The whitespace-skip loop was added in 78fcca9 (Dasel V3, ~9 months ago); line 60's indexing landed in 9bfe966 (~6 months ago). Reproduced on github.com/tomwright/dasel/[email protected].
Suggested fix
One line, between the whitespace-skip loop and the comment-skip access. Same shape as lines 69-71:
func (p *Tokenizer) parseCurRune() (Token, error) {
for p.i < p.srcLen && unicode.IsSpace(rune(p.src[p.i])) {
p.i++
}
if p.i >= p.srcLen {
return NewToken(EOF, "", p.i, 0), nil
}
if p.src[p.i] == '/' && p.i+1 < p.srcLen && p.src[p.i+1] == '/' {
Prevalence
The other two cases in this class shipped fixes two weeks ago; this one wasn't covered in those patches. I checked the rest of parseCurRune for other unguarded direct-access points after a pos++ - nothing else stood out. A testing.F harness on lexer.NewTokenizer(s).Tokenize() catches all three with trivially short inputs and would close the class.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/tomwright/dasel/v3 | ≥ 3.0.0&&< 3.11.2 | 3.11.2go get github.com/tomwright/dasel/v3@v3.11.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tomwright/dasel/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/tomwright/dasel/v3 to 3.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65gg-g7rw-6cpc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-65gg-g7rw-6cpc in your dependencies?
Find it across Go, including transitive dependencies.