Integer underflow when reporting a malformed TSIG record
Historical advisory saved 12 Nov 2026 09:55:27 UTC. The publisher may have updated it since then. Latest advisory.
osv · RUSTSEC-2026-0488
PublishedWhen a TSIG record is decoded from the DNS wire format, its MAC length and "other data" length are checked against the end of the record data. If a check failed, the error value was built from `end_idx - decoder.index()`. For a malformed record the decoder can already be past `end_idx`, so this unsigned subtraction underflows. In builds with overflow checks enabled (the `dev` profile by default) the underflow panics, so a peer that sends a crafted TSIG record can crash the process. In builds without overflow checks the result wraps and is only used in the returned error. The fix returns a plain "insufficient bytes" error without the subtraction. It is in 0.26.2.
- Source published
- 3 Sep 2026 12:00:00 UTC
- Source modified
- 12 Nov 2026 09:45:02 UTC
- Saved here
- 12 Nov 2026 09:55:27 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.