Attestkeep
Langue : Français
S'inscrire

Vulnérabilités / CVE-2022-31183

critique

CVE-2022-31183

fs2-io skips mTLS client verification

Publiée Modifiée CWE 295
Dans la Trivy database depuis au moins le 24 oct. 2026, 07:11 UTCLa date d'entrée avant ce build n'est pas enregistrée.

Sévérité par source

NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GHSA9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Le label propre à Trivy est CRITICAL. Critique selon NVD, GHSA.

Description

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.

Paquets affectés et versions corrigées

SourcePaquetCorrigé en
maven::GitHub Security Advisory Mavenco.fs2:fs2-io, co.fs2:fs2-io_2.12, co.fs2:fs2-io_2.13 et 3 autres3.2.11
Afficher les 6 entrées d'une source
SourcePaquetCorrigé en
maven::GitHub Security Advisory Mavenco.fs2:fs2-io3.2.11
maven::GitHub Security Advisory Mavenco.fs2:fs2-io_2.123.2.11
maven::GitHub Security Advisory Mavenco.fs2:fs2-io_2.133.2.11
maven::GitHub Security Advisory Mavenco.fs2:fs2-io_33.2.11
maven::GitHub Security Advisory Mavenco.fs2:fs2-io_sjs1_2.133.2.11
maven::GitHub Security Advisory Mavenco.fs2:fs2-io_sjs1_33.2.11

Références

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.