CVE-2014-3445

9.8 CRITICAL

📋 TL;DR

This vulnerability allows remote attackers to bypass authentication in HandsomeWeb SOS Webpages by using the administrator password hash instead of the cleartext password. Attackers can access backup.php without knowing the actual password, potentially gaining administrative control. All users of SOS Webpages before version 1.1.12 are affected.

💻 Affected Systems

Products:
  • HandsomeWeb SOS Webpages
Versions: All versions before 1.1.12
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires backup.php to be accessible and attacker to have obtained the administrator password hash.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the web application with administrative privileges, allowing data theft, defacement, or installation of backdoors.

🟠

Likely Case

Unauthorized access to sensitive backup files and administrative functions, potentially leading to data exposure.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH - The backup.php endpoint is typically accessible remotely, making exploitation straightforward.
🏢 Internal Only: MEDIUM - Internal attackers with access to password hashes could still exploit this vulnerability.

🎯 Exploit Status

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

Exploitation requires obtaining the administrator password hash first, which may be available through other vulnerabilities or leaks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.1.12

Vendor Advisory: http://sourceforge.net/projects/soswebpages/files/SOS%20Webpages/SOS%20Webpages%201.1.12/

Restart Required: No

Instructions:

1. Download version 1.1.12 from the vendor site. 2. Replace all existing files with the new version. 3. Verify backup.php now requires cleartext password authentication.

🔧 Temporary Workarounds

Restrict access to backup.php

all

Block external access to the vulnerable backup.php file using web server configuration.

# Apache: add to .htaccess
<Files "backup.php">
Order Deny,Allow
Deny from all
</Files>
# Nginx: add to server block
location ~ /backup\.php$ {
    deny all;
}

Remove backup.php file

linux

Delete or rename the vulnerable backup.php file if backup functionality is not required.

rm backup.php
mv backup.php backup.php.disabled

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the web application.
  • Monitor authentication logs for suspicious access attempts to backup.php.

🔍 How to Verify

Check if Vulnerable:

Check if backup.php accepts password hash instead of cleartext password by attempting authentication with a known hash.

Check Version:

Check the version number in the application's configuration files or admin interface.

Verify Fix Applied:

Verify that backup.php now rejects authentication attempts using password hashes and requires cleartext passwords.

📡 Detection & Monitoring

Log Indicators:

  • Failed authentication attempts to backup.php with unusual parameters
  • Successful access to backup.php without corresponding cleartext password authentication

Network Indicators:

  • HTTP requests to /backup.php with hash parameters in POST data

SIEM Query:

web.url="*/backup.php" AND (http.method=POST OR http.method=GET) AND (web.query="hash=*" OR http.post_data="hash=*")

🔗 References

📤 Share & Export