CVE-2021-28993
📋 TL;DR
CVE-2021-28993 is an SQL injection vulnerability in Plixer Scrutinizer 19.0.2 that allows remote attackers to execute arbitrary SQL commands. This can lead to unauthorized access to sensitive database information. Organizations running affected versions of Plixer Scrutinizer are vulnerable.
💻 Affected Systems
- Plixer Scrutinizer
📦 What is this software?
⚠️ Risk & Real-World Impact
Worst Case
Complete database compromise including exfiltration of all sensitive data, credential theft, and potential lateral movement to connected systems.
Likely Case
Extraction of sensitive configuration data, user credentials, and network monitoring information from the Scrutinizer database.
If Mitigated
Limited impact with proper input validation and database permission restrictions in place.
🎯 Exploit Status
SQL injection vulnerabilities are commonly weaponized. The description indicates remote exploitation is possible.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 19.1.0 or later
Vendor Advisory: https://docs.plixer.com/projects/scrutinizer/en/19.1.0/system/changelog.html
Restart Required: Yes
Instructions:
1. Backup current configuration and data. 2. Download Plixer Scrutinizer 19.1.0 or later from the vendor website. 3. Follow the vendor's upgrade instructions. 4. Restart the Scrutinizer service. 5. Verify the upgrade was successful.
🔧 Temporary Workarounds
Input Validation Filter
allImplement web application firewall rules to filter SQL injection patterns in HTTP requests.
WAF-specific configuration required
Network Segmentation
linuxRestrict network access to Scrutinizer to only trusted IP addresses.
firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="TRUSTED_IP" port protocol="tcp" port="443" accept'
firewall-cmd --reload
🧯 If You Can't Patch
- Implement strict network access controls to limit exposure to trusted sources only.
- Deploy a web application firewall with SQL injection detection rules in front of the Scrutinizer instance.
🔍 How to Verify
Check if Vulnerable:
Check the Scrutinizer version via the web interface or configuration files. If version is 19.0.2 or earlier, the system is vulnerable.
Check Version:
Check the web interface or configuration files for version information. No single command available.
Verify Fix Applied:
Verify the version has been updated to 19.1.0 or later and test SQL injection attempts are properly blocked.
📡 Detection & Monitoring
Log Indicators:
- Unusual database queries in Scrutinizer logs
- Multiple failed login attempts followed by successful access
- SQL syntax errors in application logs
Network Indicators:
- HTTP requests containing SQL keywords (SELECT, UNION, INSERT, etc.) to Scrutinizer endpoints
- Unusual database connection patterns
SIEM Query:
source="scrutinizer_logs" AND ("sql" OR "union" OR "select" OR "insert" OR "update" OR "delete")