CVE-2025-6531

4.3 MEDIUM

📋 TL;DR

This vulnerability allows unauthenticated access to live video streams and recorded video files from SIFUSM/MZZYG BD S1 dashcams. Attackers on the same local network can view private footage without credentials. This affects dashcams sold under various brand names with firmware up to June 11, 2025.

💻 Affected Systems

Products:
  • SIFUSM/MZZYG BD S1 dashcam and rebranded variants
Versions: All versions up to 20250611
Operating Systems: Embedded dashcam firmware
Default Config Vulnerable: ⚠️ Yes
Notes: Distributed by multiple resellers under different names. Requires RTSP service to be enabled (typically default).

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete loss of privacy as attackers can monitor live feeds and download all recorded footage, potentially capturing sensitive locations, conversations, or activities.

🟠

Likely Case

Unauthorized surveillance of dashcam footage, exposing personal or business activities recorded by the device.

🟢

If Mitigated

No access to video streams or recordings without proper authentication.

🌐 Internet-Facing: LOW - Attack requires local network access according to vulnerability description.
🏢 Internal Only: HIGH - Any attacker on the same local network can exploit this without authentication.

🎯 Exploit Status

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

Public GitHub repository contains proof-of-concept. Simple network access to RTSP endpoint (typically port 554) allows exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None known

Restart Required: No

Instructions:

No official patch available. Check manufacturer website for firmware updates beyond 20250611.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate dashcam network from other devices to limit attack surface

Disable RTSP Service

all

Turn off RTSP streaming if not required for functionality

🧯 If You Can't Patch

  • Place dashcam on isolated VLAN separate from sensitive networks
  • Implement network firewall rules to block RTSP (port 554) access except from authorized monitoring systems

🔍 How to Verify

Check if Vulnerable:

Attempt to access RTSP stream without authentication: rtsp://[dashcam-ip]:554/live

Check Version:

Check dashcam firmware version in device settings or web interface

Verify Fix Applied:

Verify authentication is required for RTSP stream access or service is disabled

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authentication attempts to RTSP endpoint
  • Unauthorized RTSP connection attempts

Network Indicators:

  • Unusual RTSP traffic patterns
  • RTSP connections from unexpected IP addresses

SIEM Query:

destination_port=554 AND NOT (source_ip IN [authorized_ips])

🔗 References

📤 Share & Export