CVE-2020-36008

8.1 HIGH

📋 TL;DR

OBottle 2.0 contains an arbitrary file write vulnerability in the \c\t.php file that allows attackers to write arbitrary files to the server. This affects all users running OBottle 2.0 with the vulnerable component accessible. The vulnerability could lead to complete system compromise.

💻 Affected Systems

Products:
  • OBottle
Versions: 2.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability is in the \c\t.php file; any installation with this file accessible is vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system takeover through remote code execution by writing malicious files like web shells or system scripts.

🟠

Likely Case

Web shell deployment leading to data theft, lateral movement, and persistence on the affected server.

🟢

If Mitigated

Limited impact if file write permissions are restricted and input validation is implemented.

🌐 Internet-Facing: HIGH - Directly accessible web applications with this vulnerability can be exploited remotely without authentication.
🏢 Internal Only: MEDIUM - Internal systems are still vulnerable but require network access; risk depends on internal segmentation.

🎯 Exploit Status

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

The GitHub issue shows exploitation details; arbitrary file write vulnerabilities are commonly weaponized for RCE.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://github.com/SomeBottle/OBottle/issues/7

Restart Required: No

Instructions:

No official patch available; check GitHub for updates or apply workarounds.

🔧 Temporary Workarounds

Remove vulnerable file

all

Delete or restrict access to the \c\t.php file to prevent exploitation.

rm /path/to/OBottle/\c\t.php

Implement input validation

all

Add strict input validation and sanitization in the PHP code to block malicious file writes.

🧯 If You Can't Patch

  • Restrict file permissions to prevent writing to critical directories.
  • Implement network segmentation and firewall rules to limit access to the vulnerable system.

🔍 How to Verify

Check if Vulnerable:

Check if \c\t.php exists in your OBottle installation and review its code for file write operations without proper validation.

Check Version:

Check OBottle version in configuration files or documentation; default is 2.0 for this vulnerability.

Verify Fix Applied:

Verify that \c\t.php is removed or patched, and test that arbitrary file writes are no longer possible.

📡 Detection & Monitoring

Log Indicators:

  • Unusual file write operations in PHP error logs, access to \c\t.php with suspicious parameters.

Network Indicators:

  • HTTP requests to \c\t.php with file write parameters, unusual outbound connections post-exploitation.

SIEM Query:

Search for '\c\t.php' in web server logs with POST/PUT methods and file-related parameters.

🔗 References

📤 Share & Export