Approved changes feed: RSS · Atom
cpe:2.3:a:typelevel:fs2:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Typelevel (ae0d1341-5b6f-53da-b68c-914a850a6910) |
|---|---|
| Product | Fs2 (bacc70f0-7168-50e4-9912-c41e486679ab) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/typelevel/fs2 |
purl2cpe | 2026-06-01 10:11:18.516701 |
pkg:maven/org.typelevel/fs2-grpc-codegen |
purl2cpe | 2026-06-01 10:11:18.516704 |
pkg:maven/org.typelevel/fs2-grpc-runtime_2.13 |
purl2cpe | 2026-06-01 10:11:18.516706 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-58369 |
vulnerable | 2026-06-08 07:35:18.056023 |
fs2: Half-shutdown of socket during TLS handshake may result in spin loop on opposite side
MEDIUM (5.3)
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.
Published: 2025-09-05T21:59:58.981Z
Updated: 2025-11-07T11:52:43.148Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31183 |
vulnerable | 2026-06-08 05:43:40.346137 |
mTLS client verification is skipped in fs2 on Node.js
CRITICAL (9.1)
fs2 is a compositional, streaming I/O library for Scala. When establishing a server-mode `TLSSocket` using `fs2-io` on Node.js, the parameter `requestCert = true` is ignored, peer certificate verification is skipped, and the connection proceeds. The vulnerability is limited to: 1. `fs2-io` running on Node.js. The JVM TLS implementation is completely independent. 2. `TLSSocket`s in server-mode. Client-mode `TLSSocket`s are implemented via a different API. 3. mTLS as enabled via `requestCert = true` in `TLSParameters`. The default setting is `false` for server-mode `TLSSocket`s. It was introduced with the initial Node.js implementation of fs2-io in 3.1.0. A patch is released in v3.2.11. The requestCert = true parameter is respected and the peer certificate is verified. If verification fails, a SSLException is raised. If using an unpatched version on Node.js, do not use a server-mode TLSSocket with requestCert = true to establish a mTLS connection.
Published: 2022-08-01T19:50:11.000Z
Updated: 2025-04-22T17:45:55.210Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.