Information disclosure via weak WebSocket handshake hashes
Published Dec 21, 2023 · Updated Nov 26, 2024
Weak cryptography in bcoin 2.2.0 allows remote attackers to obtain sensitive information through its bundled WebSocket implementation. The vendored faye-websocket.js computes WebSocket handshakes with SHA-1 in Hybi.generateAccept and MD5 in the older draft handshake signature. Published sources do not identify the sensitive data exposed, a working attack, or the precondition that turns these protocol hash operations into disclosure.
Summary
What happened
Weak cryptography in bcoin 2.2.0 allows remote attackers to obtain sensitive information through its bundled WebSocket implementation. The vendored faye-websocket.js computes WebSocket handshakes with SHA-1 in Hybi.generateAccept and MD5 in the older draft handshake signature. Published sources do not identify the sensitive data exposed, a working attack, or the precondition that turns these protocol hash operations into disclosure.
The record
- CVE
- CVE-2023-50475
- Published
- Dec 21, 2023
- Updated
- Nov 26, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 2023CVE publishedPublication date reported by the CVE source.
- Nov 26, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo