CVE-2024-47653

6.5 MEDIUM

📋 TL;DR

This vulnerability allows authenticated attackers to modify or cancel requests belonging to other users in Shilpi Client Dashboard through unauthorized API endpoints. It affects organizations using the vulnerable Shilpi Client Dashboard software. Attackers can manipulate requests they shouldn't have access to.

💻 Affected Systems

Products:
  • Shilpi Client Dashboard
Versions: Specific versions not specified in reference - all versions with vulnerable API endpoints
Operating Systems: Any OS running Shilpi Client Dashboard
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all deployments with the vulnerable API endpoints enabled. Requires authenticated access but no authorization checks.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of request management system where attackers can modify, cancel, or create fraudulent requests for any user, potentially leading to financial loss, service disruption, or data manipulation.

🟠

Likely Case

Unauthorized modification or cancellation of legitimate user requests, causing operational disruption, data integrity issues, and potential financial impact.

🟢

If Mitigated

Limited impact with proper authorization controls, logging, and monitoring in place to detect and prevent unauthorized access attempts.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but no special privileges. Attackers can use standard API calls with modified parameters.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not specified in reference - check vendor advisory

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

Restart Required: Yes

Instructions:

1. Check vendor advisory for specific patch version
2. Apply the security update from official vendor sources
3. Restart the application/service
4. Verify authorization controls are properly implemented

🔧 Temporary Workarounds

API Endpoint Restriction

all

Temporarily restrict or disable the vulnerable API endpoints until patch is applied

Configure web server/API gateway to block requests to vulnerable endpoints

Enhanced Authorization Checks

all

Implement custom middleware to verify user ownership before processing modification/cancellation requests

Add authorization checks in application code to validate user_id matches request owner

🧯 If You Can't Patch

  • Implement strict API rate limiting and monitoring for suspicious request patterns
  • Deploy web application firewall (WAF) rules to detect and block unauthorized request modifications

🔍 How to Verify

Check if Vulnerable:

Test if authenticated users can modify/cancel requests belonging to other users via API endpoints

Check Version:

Check application version through admin interface or configuration files

Verify Fix Applied:

Verify that authorization checks prevent users from modifying other users' requests

📡 Detection & Monitoring

Log Indicators:

  • Multiple modification/cancellation requests from single user for different user IDs
  • Failed authorization attempts on request modification endpoints
  • Unusual pattern of request modifications outside normal business hours

Network Indicators:

  • API calls to modification endpoints with mismatched user_id parameters
  • High volume of PUT/DELETE requests to request management endpoints

SIEM Query:

source="application_logs" AND (endpoint="*/api/requests/*/modify" OR endpoint="*/api/requests/*/cancel") AND user_id != request_owner_id

🔗 References

📤 Share & Export