13
Views
1
Comments
Request for Review: Server-Side Captcha Validation in Reactive App
Application Type
Reactive

Hi Everyone,

I’m working on implementing server-side Captcha validation in our reactive application and would appreciate your feedback.

Could you please review and share your thoughts on the following:

  1. Security Risks: Are there any potential vulnerabilities in this approach?
  2. Penetration Testing: Can this Captcha functionality be bypassed during penetration testing?
  3. Improvements: What measures can we take to strengthen the security of this Captcha implementation?

Your insights will help ensure we deliver a secure solution. Looking forward to your suggestions!



Captcha_POC.oml
2024-07-12 05-57-50
Gourav Shrivastava
Champion

Hello @Ajit Kurane 

I think your overall CAPTCHA approach looks fine, and if you follow these steps internally, your flow will be secure enough. There are some steps to verify

  • Always validate the token on the server side (never rely only on client-side checks).

  • Make each token single-use so it can’t be reused again.

  • Reject tokens that are too old (older than a few minutes).

  • Add rate limiting, for example, blocking after too many failed attempts.

  • Keep your secret keys only on the server, never exposed on the client.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.