GHSA-rrw2-px9j-qffj FS2 half-shutdown of socket during TLS handshake may result in spin loop on opposite side

• Maven co.fs2:fs2-io_2.12: >= 3.0.0-M1, < 3.12.2 → fixed in 3.12.2 • Maven co.fs2:fs2-io_2.12: >= 3.13.0-M1, < 3.13.0-M7 → fixed in 3.13.0-M7 • Maven co.fs2:fs2-io_2.13: >= 3.0.0-M1, < 3.12.2 → fixed in 3.12.2 • Maven co.fs2:fs2-io_2.13: >= 3.13.0-M1, < 3.13.0-M7 → fixed in 3.13.0-M7 • Maven co.fs2:fs2-io_3: >= 3.0.0-M1, < 3.12.2 → fixed in 3.12.2 • Maven co.fs2:fs2-io_3: >= 3.13.0-M1, < 3.13.0-M7 → fixed in 3.13.0-M7 • Maven co.fs2:fs2-io_0.26: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_0.27: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.11: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.12.0-M4: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.12.0-RC1: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.12.0-M5: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.12.0-RC2: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.13.0-M5: < 2.5.13 (no fix yet) • Maven co.fs2:fs2-io_2.12: < 2.5.13 → fixed in 2.5.13 • Maven co.fs2:fs2-io_2.13: < 2.5.13 → fixed in 2.5.13 • Maven co.fs2:fs2-io_3: < 2.5.13 → fixed in 2.5.13

Impact When establishing a TLS session using `fs2-io` on the JVM using the `fs2.io.net.tls` package, 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. This CPU is consumed until the overall connection is closed. This could be used as a denial of service attack on an fs2-io powered server -- for example, by opening many connections and putting them in a half-shutdown state. Note: this issue impacts ember backed http4s servers with HTTPS as a result of ember using fs2's TLS support. Patches Fixed in fs2 3.12.2 and 3.13.0-M7. Workarounds No workarounds. For more information If you have any questions or comments about this advisory: Open an issue. Contact the Typelevel Security Team.