{"answers":{"affected":"12 open source packages ship an affected version, including co.fs2:fs2-io, co.fs2:fs2-io_2.12 and co.fs2:fs2-io_2.13. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31183 exists.","fix":"Upgrade co.fs2:fs2-io to 3.2.11 or later.","what":"CVE-2022-31183 is a critical authentication bypass vulnerability in typelevel fs2, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31183 and fix it if it is affected.\n\nWhat it is: CVE-2022-31183 is a critical authentication bypass vulnerability in typelevel fs2, published on 1 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31183 exists.\n\nAffected packages and fixed versions:\n- co.fs2:fs2-io (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_2.12 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_2.12 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_2.13 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_2.13 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_3 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_3 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_sjs1_2.13 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_sjs1_2.13 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_sjs1_3 (Maven): affected from 3.1.0; fixed in 3.2.11\n- co.fs2:fs2-io_sjs1_3 (Maven): affected from 3.1.0; fixed in 3.2.11\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-31183/ (Markdown: https://insights.sbomify.com/CVE-2022-31183/index.md)","id":"CVE-2022-31183","markdown":"https://insights.sbomify.com/CVE-2022-31183/index.md","name":"CVE-2022-31183","record":{"aliases":["GHSA-2cpx-6pqp-wf35"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Scala streaming library","requires_auth":"none","summary":"Attackers can bypass mutual TLS client verification in fs2-io on Node.js when requestCert is enabled, allowing unauthorized connections.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fs2","vendor":"typelevel"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mTLS client verification is skipped in fs2 on Node.js","id":"CVE-2022-31183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":12,"n_references":3,"next":{"headline":"Email activation route can be abused by spammers in Discourse","id":"CVE-2022-31184"},"packages":[{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io","purl":null,"source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io","purl":"pkg:maven/co.fs2/fs2-io","source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_2.12","purl":null,"source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_2.12","purl":"pkg:maven/co.fs2/fs2-io_2.12","source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_2.13","purl":null,"source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_2.13","purl":"pkg:maven/co.fs2/fs2-io_2.13","source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_3","purl":null,"source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_3","purl":"pkg:maven/co.fs2/fs2-io_3","source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_sjs1_2.13","purl":null,"source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_sjs1_2.13","purl":"pkg:maven/co.fs2/fs2-io_sjs1_2.13","source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_sjs1_3","purl":null,"source":"GHSA-2cpx-6pqp-wf35"},{"ecosystem":"Maven","fixed":["3.2.11"],"introduced":["3.1.0"],"last_affected":[],"package":"co.fs2:fs2-io_sjs1_3","purl":"pkg:maven/co.fs2/fs2-io_sjs1_3","source":"GHSA-2cpx-6pqp-wf35"}],"prev":{"headline":"Cache poisoning via maliciously-formed request in Discourse","id":"CVE-2022-31182"},"products":["fs2"],"published":"2022-08-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["typelevel"]},"summary":"Attackers can bypass mutual TLS client verification in fs2-io on Node.js when requestCert is enabled, allowing unauthorized connections.","url":"https://insights.sbomify.com/CVE-2022-31183/"}