Technical impact
This vulnerability resides in gopacket’s SCTP packet parsing layer. Prior to version 1.7.2, the library hands attacker‑controlled chunk lengths and counts directly to several sub‑decoders without validating that each SCTP chunk contains the expected fields. The lack of bounds checks allows a crafted SCTP segment to trigger an out‑of‑bounds or inverted slice panic. When such a panic occurs, applications that have enabled SkipDecodeRecovery, IgnorePanic, or use direct registered decoders are terminated; otherwise the default recovery converts the panic into a per‑packet decode error but still consumes resources during processing. The flaw does not disclose data, modify information, or enable allocation amplification; it only interrupts packet‑processing services, resulting in a loss of availability.
Affected Systems
The gopacket library, used by Go developers for packet capture, analysis, and network protocol handling, is affected. Any application that imports gopacket prior to release 1.7.2 is vulnerable. The fix is implemented in gopacket v1.7.2 and later, so upgrade to that or newer to remediate.
Risk and Exploitability
The CVSS score of 5.9 indicates medium severity. EPSS data is not available, and the vulnerability is not listed in CISA’s KEV catalogue. Attackers can exploit the flaw by sending a malicious SCTP packet to any host that parses SCTP frames with gopacket. Based on the description, the likely attack vector is forged SCTP traffic over a network interface. If the target application has SkipDecodeRecovery or IgnorePanic enabled, the panic will crash the process; otherwise the library will report a decode error for the offending packet. In both cases the vulnerability causes a denial of service at the application or service level.
Github GHSA