Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

CVE-2023-50475

CRITICAL

CVE-2023-50475 is a critical-severity (CVSS 9.1) Broken Cryptographic Algorithm vulnerability in bsock. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2023-50475 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

bsock uses weak hashing algorithms

Also known asGHSA-jj93-39pf-7mcf
Published
Dec 21, 2023
Updated
Jul 15, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

bsocknpm
2Kdownloads / week

Description

An issue was discovered in bcoin-org bcoin version 2.2.0, allows remote attackers to obtain sensitive information via weak hashing algorithms in the component \vendor\faye-websocket.js.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmbsockall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bsock. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of bsock has shipped for CVE-2023-50475 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-50475 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-50475. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in bcoin-org bcoin version 2.2.0, allows remote attackers to obtain sensitive information via weak hashing algorithms in the component \vendor\faye-websocket.js.
O3 Security · Impact-Aware SCA

Is CVE-2023-50475 in your dependencies?

O3 detects CVE-2023-50475 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.