CVE-2025-34442

7.5 HIGH

📋 TL;DR

AVideo versions before 20.1 expose absolute server filesystem paths through public API endpoints. This information disclosure vulnerability reveals internal directory structures, which attackers can leverage to plan more targeted attacks. All AVideo installations running vulnerable versions are affected.

💻 Affected Systems

Products:
  • AVideo
Versions: All versions prior to 20.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations using default API endpoints; no special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers combine path disclosure with other vulnerabilities (like file upload or directory traversal) to achieve remote code execution, data theft, or complete system compromise.

🟠

Likely Case

Attackers map server structure to identify sensitive files, configuration weaknesses, or adjacent systems for lateral movement and privilege escalation.

🟢

If Mitigated

Limited to reconnaissance value only, with no direct data access or system modification.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires only HTTP requests to public endpoints; no authentication needed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 20.1

Vendor Advisory: https://github.com/WWBN/AVideo/commit/4a53ab2056

Restart Required: No

Instructions:

1. Backup your AVideo installation and database. 2. Update to AVideo version 20.1 or later via the built-in updater or manual installation. 3. Verify the fix by checking that API endpoints no longer return absolute paths.

🔧 Temporary Workarounds

API Endpoint Restriction

all

Restrict access to vulnerable API endpoints using web server rules or firewall.

# Example Apache .htaccess rule
RewriteRule ^api/.*$ - [F]

Web Application Firewall Rule

all

Block responses containing absolute server paths in API responses.

# WAF rule to detect path disclosure
SecRule RESPONSE_BODY "\/var\/www\/|\/home\/|C:\\" \
"id:1001,phase:4,deny,status:403,msg:'Path disclosure detected'

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate AVideo servers from sensitive systems.
  • Deploy a reverse proxy or WAF to sanitize API responses and remove path information.

🔍 How to Verify

Check if Vulnerable:

Send a GET request to any public API endpoint (e.g., /api/v1/videos) and check if the response contains absolute server paths like /var/www/avideo/...

Check Version:

Check the AVideo admin panel or inspect the version.php file in the installation directory.

Verify Fix Applied:

After patching, test the same API endpoints and confirm responses contain only relative paths or no path information.

📡 Detection & Monitoring

Log Indicators:

  • Unusual volume of requests to API endpoints, especially from unfamiliar IP addresses.

Network Indicators:

  • HTTP responses containing absolute server paths in API traffic.

SIEM Query:

source="web_server" AND uri_path="/api/*" AND response_body MATCHES "/var/www/|/home/|C:\\"

🔗 References

📤 Share & Export