Skip to content

Bump Go to 1.22 and refresh dependencies for CVE-2023-39325#29

Merged
dolph merged 1 commit into
mainfrom
claude/fix-issue-13-toolchain
May 16, 2026
Merged

Bump Go to 1.22 and refresh dependencies for CVE-2023-39325#29
dolph merged 1 commit into
mainfrom
claude/fix-issue-13-toolchain

Conversation

@dolph
Copy link
Copy Markdown
Owner

@dolph dolph commented May 16, 2026

Summary

  • Bumps the go directive in go.mod from 1.19 (EOL since August 2023) to 1.22, so the binary shipped by .github/workflows/release.yml is built against a supported toolchain.
  • Refreshes golang.org/x/net from v0.8.0 to v0.35.0, fixing CVE-2023-39325 / GHSA-4374-p667-p6c8 (HTTP/2 Rapid Reset). The connectivity tool calls net/http against user-supplied HTTPS destinations, so the unpatched dep allowed a malicious endpoint to DoS the client process.
  • Refreshes other deps along the way (x/sys, x/sync, uuid, pro-bing).

Dependency changes

Module Old New
go directive 1.19 1.22
golang.org/x/net v0.8.0 v0.35.0 (>= v0.17.0 CVE fix)
golang.org/x/sys v0.6.0 v0.30.0
golang.org/x/sync v0.1.0 v0.11.0
github.com/google/uuid v1.3.0 v1.6.0
github.com/prometheus-community/pro-bing v0.1.0 v0.6.1
github.com/google/gopacket v1.1.19 unchanged

Versions were pinned to the highest releases that still target go 1.22. Newer x/net (v0.36+), x/sys (v0.31+), and pro-bing (v0.7+) releases require go 1.23+, which would force another toolchain bump and is out of scope here. gopacket is left at v1.1.19 because upstream maintenance moved to gopacket/gopacket and that migration would require code changes — out of scope for this PR (tracked separately).

CI changes (e.g. govulncheck) are intentionally not included in this PR; that's tracked as a separate medium-priority issue.

Test Plan

  • go vet ./... passes
  • go build ./... passes
  • go test -race ./... — unit tests pass; the three TestRouteToLoopback* tests in router_test.go fail in the sandbox because the runner has no loopback route (it routes 127.0.0.0/8 over eth0 with source 192.0.2.2). These failures are environmental and unrelated to the dep bump; TestRouteToPublic, TestLookupLoopbackIp, TestLookupPublicIp, TestLookupExample, and TestLookupInvalidHostname all pass. CI should run on a runner with a normal loopback interface.
  • go.sum shows golang.org/x/net v0.35.0 (well above the v0.17.0 CVE fix threshold).

Fixes #13

https://claude.ai/code/session_01WjHPSobuzrRkjwUgjAJWMk


Generated by Claude Code

Updates the `go` directive in go.mod from 1.19 (EOL since August 2023)
to 1.22 so the shipped binary is built against a supported toolchain.

Refreshes module dependencies to pull `golang.org/x/net` past v0.17.0,
which fixes CVE-2023-39325 / GHSA-4374-p667-p6c8 (HTTP/2 Rapid Reset).
The connectivity tool uses `net/http` against user-supplied HTTPS
destinations, so this CVE made it possible for a hostile endpoint to
DoS the client process.

- go directive: 1.19 -> 1.22
- golang.org/x/net: v0.8.0 -> v0.35.0 (fixes CVE-2023-39325)
- golang.org/x/sys: v0.6.0 -> v0.30.0
- golang.org/x/sync: v0.1.0 -> v0.11.0
- github.com/google/uuid: v1.3.0 -> v1.6.0
- github.com/prometheus-community/pro-bing: v0.1.0 -> v0.6.1

Versions pinned to the highest releases that still target `go 1.22`;
newer x/net/x/sys/pro-bing releases require Go 1.23+ and would force
another toolchain bump. gopacket is left at v1.1.19 — the project
moved to gopacket/gopacket and migrating is out of scope here.

Fixes #13

https://claude.ai/code/session_01WjHPSobuzrRkjwUgjAJWMk
@dolph dolph merged commit 8de1460 into main May 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stale toolchain: Go 1.19 (EOL) and golang.org/x/net v0.8.0 (HTTP/2 Rapid Reset CVE)

2 participants