CVE-2017-17587

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to execute arbitrary SQL commands through multiple parameters in FS Indiamart Clone 1.0. Successful exploitation could lead to data theft, authentication bypass, or complete system compromise. Anyone running this specific e-commerce clone software is affected.

💻 Affected Systems

Products:
  • FS Indiamart Clone
Versions: 1.0
Operating Systems: All platforms running PHP/MySQL
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in multiple endpoints: catcompany.php, buyleads-details.php, and company/index.php

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise allowing data exfiltration, authentication bypass, privilege escalation, and potential remote code execution through database functions.

🟠

Likely Case

Unauthorized access to sensitive business data including customer information, transaction records, and company details stored in the database.

🟢

If Mitigated

Limited impact with proper input validation and database permission restrictions, potentially only allowing data viewing without modification.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Multiple public exploit scripts available, requires no authentication, and uses simple SQL injection techniques

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider replacing with secure software or implementing custom fixes.

🔧 Temporary Workarounds

Input Validation and Parameterized Queries

all

Implement proper input validation and use prepared statements/parameterized queries for all database operations

Web Application Firewall (WAF)

all

Deploy WAF with SQL injection protection rules to block malicious requests

🧯 If You Can't Patch

  • Isolate the application behind a reverse proxy with strict input filtering
  • Implement database-level controls: minimal privileges, stored procedures, and regular auditing

🔍 How to Verify

Check if Vulnerable:

Test parameters with SQL injection payloads: catcompany.php?token=1' OR '1'='1, buyleads-details.php?id=1' OR '1'='1, company/index.php?c=1' OR '1'='1

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection payloads no longer return database errors or unexpected data

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax in URL parameters
  • Multiple failed login attempts from single IP
  • Database error messages in application logs

Network Indicators:

  • HTTP requests containing SQL keywords (SELECT, UNION, etc.) in parameters
  • Unusual database query patterns

SIEM Query:

source="web_logs" AND (url="*catcompany.php*" OR url="*buyleads-details.php*" OR url="*company/index.php*") AND (param="*' OR*" OR param="*UNION*" OR param="*SELECT*" OR param="*--*" OR param="*/*")

🔗 References

📤 Share & Export