Description
A protocol compliance bug in thinbus-srp-npm versions prior to 2.0.1 causes the client to generate a fixed 252 bits of entropy instead of the intended bit length of the safe prime (defaulted to 2048 bits). RFC 5054 states in section 2.5.4 Client Key Exchange
The client key exchange message carries the client’s public value (A).
Recommendation
Update the thinbus-srp package to the latest compatible version. Followings are version details:
- Affected version(s): < 2.0.1
- Patched version(s): 2.0.1
References
Could your website be exposed too?
SmartScanner can check your website for The Thinbus Javascript Secure Remote Password (SRP) Client Generates Fewer Bits of Entropy Than Intended and gives you actionable findings to investigate.
Start a free scanRelated Issues
- MCP Inspector proxy server lacks authentication between the Inspector client and proxy - CVE-2025-49596
- Lobe Chat Desktop vulnerable to Remote Code Execution via XSS in Chat Messages - CVE-2025-59417
- Parse Javascript SDK vulnerable to prototype pollution in `Parse.Object` and internal APIs - CVE-2025-62374
- JSONPath Plus allows Remote Code Execution - CVE-2025-1302


