CVE-2024-47547

9.4 CRITICAL

📋 TL;DR

Ruijie Reyee OS versions 2.206.x through 2.319.x contain a weak password change mechanism that allows attackers to brute force authentication. This vulnerability affects all users of affected Ruijie network devices running vulnerable firmware versions.

💻 Affected Systems

Products:
  • Ruijie Reyee OS
Versions: 2.206.x up to but not including 2.320.x
Operating Systems: Ruijie proprietary OS
Default Config Vulnerable: ⚠️ Yes
Notes: Affects Ruijie network devices running Reyee OS firmware. The vulnerability is in the password change mechanism itself.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise through unauthorized administrative access, enabling network takeover, data exfiltration, and lateral movement.

🟠

Likely Case

Unauthorized access to network devices leading to configuration changes, service disruption, and credential harvesting.

🟢

If Mitigated

Limited impact with strong network segmentation, monitoring, and authentication controls in place.

🌐 Internet-Facing: HIGH - If devices are exposed to the internet, attackers can directly exploit the vulnerability without internal access.
🏢 Internal Only: HIGH - Even internally, attackers with network access can exploit this to gain administrative privileges.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires network access to the device's management interface. The weak mechanism makes brute force attacks feasible.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.320.x or later

Vendor Advisory: https://www.cisa.gov/news-events/ics-advisories/icsa-24-338-01

Restart Required: Yes

Instructions:

1. Download firmware version 2.320.x or later from Ruijie support portal. 2. Backup current configuration. 3. Upload and install new firmware via web interface or CLI. 4. Reboot device. 5. Verify firmware version.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict access to management interfaces to trusted IP addresses only.

# Configure ACL to restrict management access
# Example: ip access-list standard MGMT-ACL
# permit 192.168.1.0 0.0.0.255
# deny any

Rate Limiting

all

Implement rate limiting on authentication attempts to mitigate brute force attacks.

# Configure login attempt limits
# Example: login block-for 300 attempts 3 within 60

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach management interfaces
  • Enable comprehensive logging and monitoring for authentication attempts and failed logins

🔍 How to Verify

Check if Vulnerable:

Check firmware version via web interface (System > System Info) or CLI command 'show version'

Check Version:

show version

Verify Fix Applied:

Confirm firmware version is 2.320.x or later using same methods

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authentication attempts from single source
  • Successful logins from unusual IP addresses
  • Password change requests from unauthorized users

Network Indicators:

  • High volume of authentication requests to management interface
  • Traffic patterns consistent with brute force tools

SIEM Query:

source="ruijie_logs" (event_type="authentication_failure" count>10 within 5min) OR (event_type="password_change" from_ip not in trusted_ips)

🔗 References

📤 Share & Export