CVE-2017-11494

9.8 CRITICAL

📋 TL;DR

This CVE describes a SQL injection vulnerability in SOL.Connect ISET-mpp meter software versions 1.2.4.2 and earlier. Attackers can execute arbitrary SQL commands via the user parameter during login, potentially compromising the system. Organizations using affected versions of this energy metering software are at risk.

💻 Affected Systems

Products:
  • SOL.Connect ISET-mpp meter
Versions: 1.2.4.2 and earlier
Operating Systems: Unknown - likely embedded systems running the meter software
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the login functionality specifically via the user parameter. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing attackers to execute arbitrary SQL commands, potentially leading to data theft, authentication bypass, remote code execution, or system takeover.

🟠

Likely Case

Authentication bypass leading to unauthorized access to the metering system, potential data manipulation or extraction of sensitive information.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing SQL injection, though system may still be vulnerable to other attacks.

🌐 Internet-Facing: HIGH - The vulnerability is exploitable via login action which is typically internet-facing for remote management.
🏢 Internal Only: MEDIUM - If system is only accessible internally, risk is reduced but still significant for internal attackers or compromised internal systems.

🎯 Exploit Status

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

Exploit code is publicly available on Exploit-DB (ID 42408). The vulnerability requires no authentication and has simple exploitation vectors.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: No vendor advisory found in provided references

Restart Required: No

Instructions:

No official patch available. Upgrade to version above 1.2.4.2 if available, otherwise implement workarounds.

🔧 Temporary Workarounds

Implement Input Validation

all

Add server-side input validation to sanitize user parameter in login requests

# Application-specific implementation required
# Example: Validate user parameter contains only alphanumeric characters

Use Parameterized Queries

all

Modify login SQL queries to use parameterized statements instead of string concatenation

# Application code modification required
# Example: Use prepared statements with parameter binding

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement a web application firewall (WAF) with SQL injection protection rules

🔍 How to Verify

Check if Vulnerable:

Test login functionality with SQL injection payloads in the user parameter (e.g., ' OR '1'='1)

Check Version:

Check software version in administration interface or configuration files

Verify Fix Applied:

Attempt SQL injection attacks against the login endpoint and verify they are blocked or properly handled

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax in login attempts
  • Multiple failed login attempts with SQL-like patterns
  • Successful logins from unexpected IP addresses

Network Indicators:

  • HTTP POST requests to login endpoint containing SQL keywords in parameters
  • Unusual database query patterns following login attempts

SIEM Query:

source="web_logs" AND (uri="/login" OR uri="*/login*") AND (user="*OR*" OR user="*UNION*" OR user="*SELECT*" OR user="*INSERT*" OR user="*DELETE*")

🔗 References

📤 Share & Export