CVE-2021-47777

8.2 HIGH

📋 TL;DR

Build Smart ERP 21.0817 contains an unauthenticated SQL injection vulnerability in the login validation endpoint. Attackers can execute arbitrary SQL commands without authentication, potentially extracting or modifying database information. All systems running the vulnerable version are affected.

💻 Affected Systems

Products:
  • Build Smart ERP
Versions: 21.0817
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation of version 21.0817.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, modification, deletion, or potential remote code execution via database functions.

🟠

Likely Case

Data exfiltration of sensitive ERP information, authentication bypass, or database manipulation.

🟢

If Mitigated

Limited impact if proper network segmentation, WAF rules, and input validation are in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploit code is publicly available and requires no authentication. Simple SQL injection techniques work.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://ribccs.com/solutions/solution-buildsmart

Restart Required: No

Instructions:

1. Contact Build Smart vendor for patch information. 2. Apply any available updates. 3. Test functionality after patching.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

Implement WAF rules to block SQL injection patterns targeting the 'eidValue' parameter.

Network Segmentation

all

Restrict access to the ERP system to authorized internal networks only.

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the application code.
  • Deploy a web application firewall with SQL injection detection rules.

🔍 How to Verify

Check if Vulnerable:

Send a POST request to the login validation endpoint with payload: ';WAITFOR DELAY '0:0:3'-- in the eidValue parameter and observe delayed response.

Check Version:

Check ERP system version in admin interface or configuration files.

Verify Fix Applied:

Test with the same payload and ensure no SQL injection occurs and response time is normal.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed login attempts with SQL patterns
  • Long database query execution times

Network Indicators:

  • HTTP POST requests to login endpoint containing SQL keywords like WAITFOR, SELECT, UNION

SIEM Query:

source="web_logs" AND (uri="/login_validation" OR uri="*login*") AND (request_body="*WAITFOR*" OR request_body="*SELECT*" OR request_body="*UNION*")

🔗 References

📤 Share & Export