- In applications registration , it required a mobile number for compulsory 2 factor authentication.
- Captured the request for mobile number addition
POST /mobile/add
{XXNUMBERXX}
(1/n)
- Now followed the registration normally by adding a mobile number.
- Now when I login to account it required an otp to proceed.
- Used an invalid otp like 111111 and intercepted the request.
- Changed the request PATH and BODY to earlier captured request.
(2/n)
- They we’re implementing checks for all internal api endpoints before entering otp but forget to add check for mobile number addition request.
- I was able to add a new number without entering otp
- This led to 2fa bypass.
An insecure CORS configuration allows any website to trigger requests with user credentials to the target application and read the responses thus enabling attackers to perform privileged actions or to retrieve potential sensitive information
1. Cyber Work 2. Click Here 3. Defrag This 4. Security Now 5. InfoSec Real 6. InfoSec Live 7. Simply Cyber 8. OWASP Podcast 9. We Talk Cyber 10. Risky Business 11. Malicious Life 12. Hacking Humans 13. What The Shell 14. Life of a CISO 15. H4unt3d Hacker 16. 2 Cyber Chicks
17. The Hacker Mind 18. Security Weekly 19. Cyberside Chats 20. Darknet Diaries 21. CyberWire Daily 22. Absolute AppSec 23. Security in Five 24. Smashing Security 25. 401 Access Denied 26. 7 Minute Security 27. 8th Layer Insights 28. Adopting Zero Trust 29. Cyber Security Sauna