CVE-2023-3377

9.8 CRITICAL

📋 TL;DR

This SQL injection vulnerability in Veribilim Software Computer Veribase allows attackers to execute arbitrary SQL commands through specially crafted inputs. It affects all Veribase versions through November 23, 2023. Organizations using this software are at risk of data breaches and system compromise.

💻 Affected Systems

Products:
  • Veribilim Software Computer Veribase
Versions: through 20231123
Operating Systems: Unknown - likely Windows-based given vendor context
Default Config Vulnerable: ⚠️ Yes
Notes: All installations up to November 23, 2023 are vulnerable. No specific configuration details provided in CVE.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data exfiltration, data destruction, privilege escalation to system-level access, and potential lateral movement to other systems.

🟠

Likely Case

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

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permissions restricting unauthorized actions.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

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

SQL injection vulnerabilities typically have low exploitation complexity. The vendor did not respond to disclosure attempts.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

1. Contact Veribilim Software for patch information. 2. If no patch available, implement workarounds. 3. Consider migrating to alternative software if vendor is unresponsive.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy WAF with SQL injection rules to block malicious requests

Input Validation

all

Implement strict input validation on all user inputs to the application

🧯 If You Can't Patch

  • Isolate the Veribase system from internet access and restrict internal network access
  • Implement database-level controls: use least privilege accounts, enable audit logging, and restrict database permissions

🔍 How to Verify

Check if Vulnerable:

Check Veribase version against affected range (through 20231123). Test with SQL injection payloads in input fields if authorized.

Check Version:

Check application interface or configuration files for version information

Verify Fix Applied:

Verify version is newer than 20231123. Test SQL injection attempts should be blocked or properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual database queries
  • SQL syntax errors in application logs
  • Multiple failed login attempts with SQL-like patterns

Network Indicators:

  • Unusual outbound database connections
  • Large data transfers from database server

SIEM Query:

source="veribase" AND (message="*sql*" OR message="*select*" OR message="*union*" OR message="*or 1=1*")

🔗 References

📤 Share & Export