[MoBP] Windows socket exhaustion
Summary: PortSwigger Research describes a Windows socket exhaustion problem that occurs when Burp Sequencer or Intruder issue a large number of requests in quick succession, because Windows leaves a socket in an open state for a short period after close() is called. The new Burp release detects the problem and responds by rapidly throttling back its requests, then reissues the failed requests and resumes once normal network service returns, usually in under a minute.
Key Takeaway: A lengthy Intruder data-harvesting run could lose large chunks of its work to connection failures, and the only prior fix was a Registry tweak that, in PortSwigger's assessment, hardly anyone applies.
Read the original at PortSwigger Research ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026