The Thinbus Javascript Secure Remote Password (SRP) Client Generates Fewer Bits of Entropy Than Intended

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

• GHSA-8q6v-474h-whgg
• CVE-2025-54885
• CWE-331
• CAPEC-310
• OWASP 2021-A2
• OWASP 2021-A6

Related Issues

• Trix allows Cross-site Scripting via `javascript:` url in a link - CVE-2025-21610
• Nuxt has Client-Side Path Traversal in Nuxt Island Payload Revival - CVE-2025-59414
• Lobe Chat Desktop vulnerable to Remote Code Execution via XSS in Chat Messages - CVE-2025-59417
• DocsGPT Allows Remote Code Execution - CVE-2025-0868

You might also like:

How to Secure your NodeJs Express Javascript Application - part 2

How to Secure your NodeJs Express Javascript Application - part 1

10 Secure Coding Best Practices to Follow in Every Project

Tags:

npm

thinbus-srp