CVE-2025-65407

6.5 MEDIUM

📋 TL;DR

This vulnerability is a use-after-free flaw in Live555 Streaming Media's MPEG1or2Demux component that allows attackers to cause denial of service by sending specially crafted MPEG Program streams. Systems using Live555 for media streaming are affected, particularly those processing untrusted MPEG content. The vulnerability can crash the media server, disrupting streaming services.

💻 Affected Systems

Products:
  • Live555 Streaming Media
Versions: v2018.09.02 and potentially earlier versions
Operating Systems: All platforms running Live555
Default Config Vulnerable: ⚠️ Yes
Notes: Any system using Live555 to process MPEG Program streams is vulnerable. The vulnerability is in the demuxer component.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete service disruption with potential for remote code execution if combined with other vulnerabilities, though CVE-2025-65407 alone only causes DoS.

🟠

Likely Case

Service crashes and denial of service when processing malicious MPEG streams, requiring service restart.

🟢

If Mitigated

Minimal impact if proper input validation and memory safety controls are implemented.

🌐 Internet-Facing: HIGH - Streaming servers exposed to internet can be targeted with crafted MPEG streams.
🏢 Internal Only: MEDIUM - Internal media processing systems could be exploited by internal attackers or through compromised content.

🎯 Exploit Status

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

Exploitation requires crafting a malicious MPEG Program stream. No authentication needed as it targets the media processing component.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: Not available

Restart Required: Yes

Instructions:

1. Monitor Live555 repository for security updates
2. Apply patch when available
3. Recompile and redeploy Live555
4. Restart all services using Live555

🔧 Temporary Workarounds

Input Validation Filter

all

Implement network filtering to block or sanitize MPEG Program streams from untrusted sources

Service Isolation

linux

Run Live555 in isolated containers with resource limits to contain crashes

docker run --memory=512m --cpus=1 -d live555-container

🧯 If You Can't Patch

  • Implement strict network segmentation to limit access to Live555 services
  • Deploy WAF or IPS rules to detect and block malicious MPEG streams

🔍 How to Verify

Check if Vulnerable:

Check if system uses Live555 v2018.09.02 or earlier and processes MPEG streams

Check Version:

Check Live555 source code or build configuration for version information

Verify Fix Applied:

Verify Live555 version is updated beyond v2018.09.02 when patch is available

📡 Detection & Monitoring

Log Indicators:

  • Live555 process crashes
  • Segmentation fault errors in system logs
  • Abnormal termination of media streaming services

Network Indicators:

  • Unusual MPEG stream patterns
  • Multiple connection attempts with malformed media data

SIEM Query:

source="live555.log" AND ("segmentation fault" OR "crash" OR "SIGSEGV")

🔗 References

📤 Share & Export