fs2: Half-shutdown of socket during TLS handshake may result in spin loop on opposite side
typelevel fs2
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| co.fs2:fs2-io_2.12 Maven |
|
|
| co.fs2:fs2-io_2.13 Maven |
typelevel fs2
| Product | Affected | Fixed in |
|---|---|---|
| co.fs2:fs2-io_2.12 Maven |
|
|
| co.fs2:fs2-io_2.13 Maven |
≥ 3.0.0-M1 · < 3.12.2≥ 3.13.0-M1 · < 3.13.0-M7< 2.5.13
|
| co.fs2:fs2-io_3 Maven |
|
|
| co.fs2:fs2-io_0.26 Maven |
| No fix yet |
| co.fs2:fs2-io_0.27 Maven |
| No fix yet |
| co.fs2:fs2-io_2.11 Maven |
| No fix yet |
| co.fs2:fs2-io_2.12.0-M4 Maven |
| No fix yet |
| co.fs2:fs2-io_2.12.0-RC1 Maven |
| No fix yet |
| co.fs2:fs2-io_2.12.0-M5 Maven |
| No fix yet |
| co.fs2:fs2-io_2.12.0-RC2 Maven |
| No fix yet |
| co.fs2:fs2-io_2.13.0-M5 Maven |
| No fix yet |
fs2 is a compositional, streaming I/O library for Scala. Versions up to and including 2.5.12, 3.0.0-M1 through 3.12.2, and 3.13.0-M1 through 3.13.0-M6 are vulnerable to denial of service attacks though TLS sessions using fs2-io on the JVM using the fs2.io.net.tls package. When establishing a TLS session, if one side of the connection shuts down `write` while the peer side is awaiting more data to progress the TLS handshake, the peer side will spin loop on the socket read, fully utilizing a CPU. The CPU is consumed until the overall connection is closed, potentially shutting down a fs2-io powered server. This issue is fixed in versions 2.5.13, 3.12.1, and 3.13.0-M7.
From the CVE record · GitHub_M
The JVM fs2.io.net.tls package can spin on a socket read during a TLS handshake if one side shuts down writing while its peer awaits more data. This can consume a full CPU until the connection closes, potentially shutting down an fs2-io-powered server.
Teams using Maven co.fs2:fs2-io_2.12, fs2-io_2.13, or fs2-io_3 should check affected releases before 2.5.13 or 3.12.2, or from 3.13.0-M1 through 3.13.0-M6; the listed older package variants have no fixed version.