CVE-2024-47654

7.5 HIGH

📋 TL;DR

This vulnerability allows unauthenticated attackers to send unlimited OTP requests to Shilpi Client Dashboard systems, causing OTP bombing attacks that can overwhelm systems or harass users. It affects all deployments of Shilpi Client Dashboard with vulnerable API endpoints exposed.

💻 Affected Systems

Products:
  • Shilpi Client Dashboard
Versions: All versions prior to patch
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects systems with OTP functionality enabled via vulnerable API endpoints.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system denial-of-service through resource exhaustion, SMS/email provider blacklisting due to spam, and potential account lockouts for legitimate users.

🟠

Likely Case

Service disruption through OTP flooding, increased operational costs from SMS/email charges, and user harassment through repeated OTP notifications.

🟢

If Mitigated

Minimal impact with proper rate limiting and CAPTCHA controls preventing automated OTP requests.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Simple HTTP request flooding with no authentication required.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific version

Vendor Advisory: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2024-0313

Restart Required: Yes

Instructions:

1. Check vendor advisory for patch availability
2. Apply vendor-provided security update
3. Restart application services
4. Verify rate limiting and CAPTCHA are enabled

🔧 Temporary Workarounds

Implement Web Application Firewall Rules

all

Configure WAF to limit OTP request frequency per IP

WAF-specific configuration commands

API Gateway Rate Limiting

all

Add rate limiting at API gateway level for OTP endpoints

API gateway specific configuration

🧯 If You Can't Patch

  • Implement network-level rate limiting using firewall rules
  • Disable OTP functionality if not essential

🔍 How to Verify

Check if Vulnerable:

Test OTP endpoint with rapid consecutive requests without CAPTCHA

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Verify rate limiting blocks excessive OTP requests and CAPTCHA is required

📡 Detection & Monitoring

Log Indicators:

  • High frequency of OTP requests from single IP
  • Failed OTP attempts without CAPTCHA validation

Network Indicators:

  • Unusual volume of requests to OTP API endpoints
  • Requests bypassing CAPTCHA validation

SIEM Query:

source_ip=* AND uri_path="*/otp/*" AND count > 10 within 60s

🔗 References

📤 Share & Export