CVE-2022-48592

8.8 HIGH

📋 TL;DR

This SQL injection vulnerability in ScienceLogic SL1 allows attackers to execute arbitrary SQL commands through the vendor_country parameter in the vendor print report feature. This could lead to data theft, modification, or deletion. All ScienceLogic SL1 users with the vulnerable version are affected.

💻 Affected Systems

Products:
  • ScienceLogic SL1
Versions: Versions prior to 11.3.2
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the vendor print report feature specifically. Requires access to the SL1 interface.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data exfiltration, privilege escalation, and potential remote code execution on the database server.

🟠

Likely Case

Unauthorized data access, data manipulation, and potential extraction of sensitive information from the database.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing SQL injection.

🌐 Internet-Facing: HIGH - If the SL1 interface is exposed to the internet, attackers can directly exploit this vulnerability.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this vulnerability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

SQL injection vulnerabilities are typically easy to exploit with basic knowledge. Requires authenticated access to the vulnerable feature.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 11.3.2 and later

Vendor Advisory: https://www.sciencelogic.com/

Restart Required: Yes

Instructions:

1. Backup your SL1 configuration and database. 2. Download and install SL1 version 11.3.2 or later from the ScienceLogic support portal. 3. Follow the official upgrade documentation. 4. Restart SL1 services after installation.

🔧 Temporary Workarounds

Disable vendor print report feature

all

Temporarily disable or restrict access to the vulnerable vendor print report feature.

Implement WAF rules

all

Add SQL injection detection and blocking rules to your web application firewall.

🧯 If You Can't Patch

  • Implement strict input validation and sanitization for the vendor_country parameter
  • Use parameterized queries or stored procedures instead of dynamic SQL

🔍 How to Verify

Check if Vulnerable:

Check if your SL1 version is below 11.3.2 and if the vendor print report feature is accessible.

Check Version:

Check the SL1 web interface under Administration > System > About or use the SL1 CLI command: sl1 version

Verify Fix Applied:

Verify installation of version 11.3.2 or later and test the vendor print report feature with SQL injection test payloads.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts followed by vendor print report access
  • SQL syntax errors in application logs

Network Indicators:

  • Unusual database connection patterns
  • SQL injection patterns in HTTP requests to vendor print report endpoint

SIEM Query:

source="sl1_logs" AND (vendor_country="*' OR *" OR vendor_country="*;*" OR vendor_country="*--*")

🔗 References

📤 Share & Export