GHSA-RRW2-PX9J-QFFJ
Vulnerability from github – Published: 2025-09-05 20:58 – Updated: 2025-11-07 12:29Impact
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": "3.0.0-M1"
},
{
"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": "3.0.0-M1"
},
{
"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": "3.0.0-M1"
},
{
"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 2.5.13"
},
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_0.26"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 2.5.13"
},
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_0.27"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 2.5.13"
},
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_2.11"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 2.5.13"
},
"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 2.5.13"
},
"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 2.5.13"
},
"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 2.5.13"
},
"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 2.5.13"
},
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_2.13.0-M5"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_2.12"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.5.13"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_2.13"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.5.13"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "co.fs2:fs2-io_3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.5.13"
}
],
"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-11-07T12:29:27Z",
"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/pull/3624"
},
{
"type": "WEB",
"url": "https://github.com/typelevel/fs2/commit/46e2dc3abf994dcf3d0b804b2ddb3c10c04d4976"
},
{
"type": "WEB",
"url": "https://github.com/typelevel/fs2/commit/5c6c4c6c1ef330f7e6b53661ecc63d5f5ba8885c"
},
{
"type": "WEB",
"url": "https://github.com/typelevel/fs2/commit/edf0c4f2e660360d1c1a8c5377ce32294de89238"
},
{
"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"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.