CVE-2020-24214

9.8 CRITICAL

📋 TL;DR

This vulnerability allows unauthenticated attackers to send crafted RTSP requests to HiSilicon-based video encoders, causing a buffer overflow that crashes the application. The device becomes unable to encode or stream video for up to a minute until it automatically reboots, effectively disabling it if attacks are repeated. Organizations using affected HiSilicon IPTV/H.264/H.265 video encoders are at risk.

💻 Affected Systems

Products:
  • HiSilicon-based IPTV/H.264/H.265 video encoders
Versions: Unknown specific versions, but likely multiple firmware versions
Operating Systems: Embedded Linux systems on HiSilicon hardware
Default Config Vulnerable: ⚠️ Yes
Notes: Devices with RTSP services exposed to untrusted networks are particularly vulnerable. The vulnerability affects the box application specifically.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers can send malicious requests once per minute to perpetually disable video encoding and streaming capabilities, creating sustained denial of service for surveillance, broadcasting, or monitoring systems.

🟠

Likely Case

Attackers exploit this to cause repeated device crashes and reboots, disrupting video services for extended periods and potentially creating security blind spots.

🟢

If Mitigated

With proper network segmentation and access controls, impact is limited to isolated network segments with minimal service disruption.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit code is publicly available on Packet Storm Security and other sources. Attack requires only network access to RTSP port (typically 554).

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: No official vendor advisory found

Restart Required: No

Instructions:

No official patch available. Check with device manufacturer for firmware updates. Consider replacing affected devices with patched versions if available.

🔧 Temporary Workarounds

Network Segmentation and Access Control

linux

Restrict RTSP port (typically 554) access to trusted networks only using firewall rules

iptables -A INPUT -p tcp --dport 554 -s trusted_network -j ACCEPT
iptables -A INPUT -p tcp --dport 554 -j DROP

RTSP Service Disablement

all

Disable RTSP service if not required for device functionality

Check device configuration interface for RTSP service toggle

🧯 If You Can't Patch

  • Isolate affected devices in separate VLAN with strict access controls
  • Implement network monitoring for abnormal RTSP traffic patterns

🔍 How to Verify

Check if Vulnerable:

Test by sending crafted RTSP request to port 554 and observing if device crashes/reboots. Use public PoC scripts with caution in test environment only.

Check Version:

Check device web interface or console for firmware version. Command varies by manufacturer.

Verify Fix Applied:

After applying workarounds, test that RTSP service is either inaccessible from untrusted networks or disabled entirely.

📡 Detection & Monitoring

Log Indicators:

  • Device reboot logs
  • Application crash logs
  • Abnormal RTSP connection attempts

Network Indicators:

  • Malformed RTSP packets to port 554
  • Repeated connection attempts to RTSP service
  • Traffic patterns matching known exploit signatures

SIEM Query:

source_port=554 AND (payload_contains="RTSP" AND payload_size>threshold) OR device_reboot_event

🔗 References

📤 Share & Export