CVE-2024-50706

9.8 CRITICAL

📋 TL;DR

This is an unauthenticated SQL injection vulnerability in Uniguest Tripleplay version 23.1+ that allows remote attackers to execute arbitrary SQL queries on the backend database. It affects all systems running vulnerable versions of Uniguest Tripleplay software.

💻 Affected Systems

Products:
  • Uniguest Tripleplay
Versions: 23.1 and later versions
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments of affected versions are vulnerable by default.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the backend database including data theft, data destruction, privilege escalation, and potential remote code execution on the database server.

🟠

Likely Case

Data exfiltration, database manipulation, and potential lateral movement to other systems through database connections.

🟢

If Mitigated

Limited impact due to network segmentation, database permissions restrictions, and input validation controls.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

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

SQL injection vulnerabilities are commonly weaponized and this requires no authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched version

Vendor Advisory: https://uniguest.com/cve-bulletins/

Restart Required: Yes

Instructions:

1. Review vendor advisory at provided URL. 2. Download and apply the latest patched version from Uniguest. 3. Restart the Tripleplay service. 4. Verify the patch is applied successfully.

🔧 Temporary Workarounds

Network Segmentation

linux

Restrict network access to Tripleplay systems to only trusted sources

Use firewall rules to limit access: iptables -A INPUT -s trusted_network -p tcp --dport tripleplay_port -j ACCEPT
iptables -A INPUT -p tcp --dport tripleplay_port -j DROP

Web Application Firewall

all

Deploy WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate vulnerable systems
  • Deploy database activity monitoring and alert on suspicious SQL queries

🔍 How to Verify

Check if Vulnerable:

Check Tripleplay version number in admin interface or configuration files

Check Version:

Check Tripleplay admin dashboard or configuration files for version information

Verify Fix Applied:

Verify version is updated to patched release and test SQL injection attempts are blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL query patterns in database logs
  • Multiple failed login attempts from single IP
  • Unexpected database schema changes

Network Indicators:

  • SQL injection patterns in HTTP requests to Tripleplay endpoints
  • Unusual outbound database connections

SIEM Query:

source="tripleplay_logs" AND ("sql" OR "database" OR "injection")

🔗 References

📤 Share & Export