ghsa-rrw2-px9j-qffj
Vulnerability from github
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.
{ "affected": [ { "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.12" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "3.12.2" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.12" }, "ranges": [ { "events": [ { "introduced": "3.13.0-M1" }, { "fixed": "3.13.0-M7" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.13" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "3.12.2" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.13" }, "ranges": [ { "events": [ { "introduced": "3.13.0-M1" }, { "fixed": "3.13.0-M7" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_3" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "3.12.2" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_3" }, "ranges": [ { "events": [ { "introduced": "3.13.0-M1" }, { "fixed": "3.13.0-M7" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_0.26" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_0.27" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.11" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.12.0-M4" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.12.0-RC1" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.12.0-M5" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.12.0-RC2" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] }, { "database_specific": { "last_known_affected_version_range": "\u003c 3.12.2" }, "package": { "ecosystem": "Maven", "name": "co.fs2:fs2-io_2.13.0-M5" }, "ranges": [ { "events": [ { "introduced": "0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-58369" ], "database_specific": { "cwe_ids": [ "CWE-400" ], "github_reviewed": true, "github_reviewed_at": "2025-09-05T20:58:23Z", "nvd_published_at": "2025-09-05T22:15:34Z", "severity": "MODERATE" }, "details": "### Impact\nWhen 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.\n\nThis 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.\n\nNote: this issue impacts ember backed http4s servers with HTTPS as a result of ember using fs2\u0027s TLS support.\n\n### Patches\nFixed in fs2 3.12.2 and 3.13.0-M7.\n\n### Workarounds\nNo workarounds.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n[Open an issue.](https://github.com/typelevel/fs2/issues/new/choose)\nContact the [Typelevel Security Team](https://github.com/typelevel/.github/blob/main/SECURITY.md).", "id": "GHSA-rrw2-px9j-qffj", "modified": "2025-09-10T20:50:04Z", "published": "2025-09-05T20:58:23Z", "references": [ { "type": "WEB", "url": "https://github.com/typelevel/fs2/security/advisories/GHSA-rrw2-px9j-qffj" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-58369" }, { "type": "WEB", "url": "https://github.com/typelevel/fs2/issues/3590" }, { "type": "WEB", "url": "https://github.com/typelevel/fs2/commit/46e2dc3abf994dcf3d0b804b2ddb3c10c04d4976" }, { "type": "WEB", "url": "https://github.com/typelevel/fs2/commit/5c6c4c6c1ef330f7e6b53661ecc63d5f5ba8885c" }, { "type": "PACKAGE", "url": "https://github.com/typelevel/fs2" }, { "type": "WEB", "url": "https://github.com/typelevel/fs2/releases/tag/v3.12.2" }, { "type": "WEB", "url": "https://github.com/typelevel/fs2/releases/tag/v3.13.0-M7" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "type": "CVSS_V3" } ], "summary": "FS2 half-shutdown of socket during TLS handshake may result in spin loop on opposite side" }
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.