CVE-2023-29790

7.5 HIGH

📋 TL;DR

Kodbox versions 1.2.x through 1.3.7 have a sensitive information leakage vulnerability that allows attackers to access confidential data without authentication. This affects all organizations using vulnerable kodbox installations, particularly those with internet-facing deployments.

💻 Affected Systems

Products:
  • kodbox
Versions: 1.2.x through 1.3.7
Operating Systems: All platforms running kodbox
Default Config Vulnerable: ⚠️ Yes
Notes: All installations within the affected version range are vulnerable regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could access sensitive configuration files, database credentials, or user data, potentially leading to full system compromise and data exfiltration.

🟠

Likely Case

Unauthenticated attackers accessing exposed sensitive files containing configuration details or temporary data.

🟢

If Mitigated

Limited impact with proper network segmentation and access controls preventing external exploitation.

🌐 Internet-Facing: HIGH - Unauthenticated exploitation allows external attackers to access sensitive information directly.
🏢 Internal Only: MEDIUM - Internal attackers could still exploit this, but requires network access to the vulnerable system.

🎯 Exploit Status

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

The vulnerability appears to be simple to exploit based on available information, requiring minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.3.8 or later

Vendor Advisory: https://blog.mo60.cn/index.php/archives/kodbox.html

Restart Required: No

Instructions:

1. Backup your kodbox installation and data. 2. Download the latest version from the official kodbox website. 3. Replace the existing installation files with the updated version. 4. Verify the version is now 1.3.8 or higher.

🔧 Temporary Workarounds

Restrict Access via Web Server

all

Configure web server to block access to sensitive directories and file patterns

# For Apache: Add to .htaccess
<FilesMatch "\.(php|inc|conf|sql|log)$">
    Order allow,deny
    Deny from all
</FilesMatch>
# For Nginx: Add to server block
location ~ \.(php|inc|conf|sql|log)$ {
    deny all;
}

🧯 If You Can't Patch

  • Implement strict network access controls to limit access to kodbox installation only to authorized users
  • Deploy a web application firewall (WAF) with rules to block sensitive file access patterns

🔍 How to Verify

Check if Vulnerable:

Check if accessing sensitive files like configuration files or logs is possible without authentication via browser or curl

Check Version:

Check kodbox version in admin panel or look for version file in installation directory

Verify Fix Applied:

After updating, attempt to access previously vulnerable paths and confirm access is denied

📡 Detection & Monitoring

Log Indicators:

  • Multiple 200 OK responses to sensitive file requests
  • Access to files with extensions like .conf, .inc, .sql, .log from unauthorized IPs

Network Indicators:

  • HTTP requests to sensitive file paths without authentication
  • Unusual file access patterns to non-public directories

SIEM Query:

source="web_server_logs" AND (status=200 AND (uri="*.conf" OR uri="*.inc" OR uri="*.sql" OR uri="*.log"))

🔗 References

📤 Share & Export