SCTP needs to better-check INIT ACK chunk parameters
illumos-gate · OmniOS · Triton Data Center SmartOS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| illumos illumos-gate |
| No fix yet |
| OmniOS OmniOS |
| No fix yet |
| Triton Data Center SmartOS |
illumos-gate · OmniOS · Triton Data Center SmartOS
| Product | Affected | Fixed in |
|---|---|---|
| illumos illumos-gate |
| No fix yet |
| OmniOS OmniOS |
| No fix yet |
| Triton Data Center SmartOS |
|
| No fix yet |
The illumos SCTP inbound path performs association lookup for INIT ACK chunks without adequately validating the address parameters carried in the chunk. Since this lookup runs during packet classification (i.e. before SCTP integrity checks or IPsec policy are applied) a remote, unauthenticated attacker can send a crafted SCTP INIT ACK packet with malformed address parameters to cause an out-of-bounds access and kernel heap corruption, which may lead to remote code execution. The flaw has existed since 2010 (illumos-gate commit a5407c02), and affects any illumos distribution prior to illumos-gate commit 53a3efde.
From the CVE record · illumos
The illumos SCTP inbound path does not adequately validate address parameters in INIT ACK chunks before association lookup. A remote, unauthenticated attacker can send a crafted packet that causes an out-of-bounds access and kernel heap corruption, potentially leading to remote code execution; no user interaction is required.
Operators of illumos distributions, including OmniOS and Triton Data Center SmartOS, should check systems built from illumos-gate before commit 53a3efde.