No validation of attacker-supplied STP timer values from winning root bridge BPDU
Summary
bstp_record_config_timeout_values(:393-401): blindly copies cu_max_age/cu_hello_time/cu_forward_delay from received Config BPDU into sc values with no range validation. uint16 from ntohs of attacker BPDU(:926-928). IEEE 802.1D-2004 mandates max_age 6-40s hello 1-10s forward_delay 4-30s. Setting to 0 causes immediate timer expiry -> instant BPDU age-out or skip LISTENING/LEARNING -> rapid destabilizing topology changes. Inherent to STP trust model but lack of clamping amplifies DoS. Fix: clamp to IEEE ranges.
Discussion (0)
PoC verification
Evidence pack
findings/poc/DF-0483 Β· 1 files| File | Type | Description | Size | |
|---|---|---|---|---|
| manifest.json | file | 391 B | view raw |
Fix verification
not_testablerecommended fix identified; fix.diff not authored/validated in this batch
recommended fix identified; fix.diff not authored/validated in this batch
Confirmed kernel references
β
Detail
Exploit chain
none (Info severity)
Evidence (decisive lines)
Source-confirmed at sys/net/bridge/bridgestp.c:393: no validation of attacker-supplied STP timer values
Verified recommended fix
Source-confirmed at sys/net/bridge/bridgestp.c:393: no validation of attacker-supplied STP timer values
Verdict
Source-confirmed at sys/net/bridge/bridgestp.c:393: no validation of attacker-supplied STP timer values
No comments yet.