CVE-2021-43700

9.8 CRITICAL

📋 TL;DR

CVE-2021-43700 is a SQL injection vulnerability in ApiManager 1.1 that allows attackers to execute arbitrary SQL commands through the /index.php?act=api&tag=8 endpoint. This affects all users running ApiManager 1.1 without proper input validation. Attackers can potentially access, modify, or delete database contents.

💻 Affected Systems

Products:
  • ApiManager
Versions: 1.1
Operating Systems: All platforms running ApiManager
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of ApiManager 1.1 are vulnerable by default. The vulnerability exists in the core code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via subsequent attacks.

🟠

Likely Case

Unauthorized data access, data manipulation, or privilege escalation within the database.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permissions in place.

🌐 Internet-Facing: HIGH - The vulnerable endpoint is directly accessible via web requests.
🏢 Internal Only: MEDIUM - Internal attackers could exploit this if they have network access to the system.

🎯 Exploit Status

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

The GitHub issue shows exploitation details. SQL injection is well-understood and easily weaponized.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch exists. Consider upgrading to a maintained fork or implementing workarounds.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize user inputs before processing SQL queries.

Modify /index.php to validate and sanitize the 'tag' parameter using prepared statements or whitelisting.

Web Application Firewall (WAF)

all

Deploy a WAF to block SQL injection attempts at the network layer.

Configure WAF rules to block SQL injection patterns targeting /index.php?act=api&tag=*

🧯 If You Can't Patch

  • Disable or restrict access to the vulnerable endpoint using network ACLs or web server configuration.
  • Implement database-level controls: use least privilege accounts, enable auditing, and restrict database permissions.

🔍 How to Verify

Check if Vulnerable:

Test the endpoint with SQL injection payloads like /index.php?act=api&tag=8' OR '1'='1 and observe database errors or unexpected behavior.

Check Version:

Check the software version in the application interface or configuration files.

Verify Fix Applied:

After applying workarounds, retest with SQL injection payloads to ensure they are blocked or sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • HTTP requests to /index.php?act=api&tag= with SQL keywords like UNION, SELECT, OR

Network Indicators:

  • HTTP traffic containing SQL injection patterns in query parameters

SIEM Query:

source="web_logs" AND uri="/index.php" AND query="*act=api*" AND (query="*UNION*" OR query="*SELECT*" OR query="*OR*" OR query="*'*" OR query="*--*" OR query="*;*")

🔗 References

📤 Share & Export