CVE-2022-22986

8.8 HIGH

📋 TL;DR

This vulnerability allows an attacker on the same network segment to execute arbitrary operating system commands on Netcommunity OG410X and OG810X series devices by uploading a specially crafted configuration file. This affects organizations using these specific network devices with vulnerable firmware versions. Attackers can gain full control of affected devices without authentication.

💻 Affected Systems

Products:
  • Netcommunity OG410Xa
  • Netcommunity OG410Xi
  • Netcommunity OG810Xa
  • Netcommunity OG810Xi
Versions: Firmware version 2.28 and earlier
Operating Systems: Embedded firmware
Default Config Vulnerable: ⚠️ Yes
Notes: All devices with vulnerable firmware are affected regardless of configuration. Attack requires adjacent network access.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of network device leading to network infiltration, data exfiltration, lateral movement to other systems, and persistent backdoor installation.

🟠

Likely Case

Attacker gains administrative control of network device, enabling network traffic interception, configuration changes, and potential denial of service.

🟢

If Mitigated

Limited impact due to network segmentation and strict access controls preventing adjacent network access to vulnerable devices.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation requires network adjacency but no authentication. Crafted config file upload leads to command injection.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Firmware version 2.29 or later

Vendor Advisory: https://business.ntt-east.co.jp/topics/2022/03_22.html

Restart Required: Yes

Instructions:

1. Download firmware version 2.29 or later from vendor portal. 2. Backup current configuration. 3. Upload new firmware via web interface. 4. Reboot device. 5. Verify firmware version.

🔧 Temporary Workarounds

Network Segmentation

all

Isolate vulnerable devices on separate VLANs with strict access controls

Access Control Lists

all

Implement ACLs to restrict who can access device management interfaces

🧯 If You Can't Patch

  • Segment vulnerable devices on isolated network segments with no trusted systems
  • Implement strict firewall rules to block all unnecessary traffic to device management interfaces

🔍 How to Verify

Check if Vulnerable:

Check firmware version via device web interface or CLI. If version is 2.28 or earlier, device is vulnerable.

Check Version:

Check via web interface: System > Firmware Information or via CLI: show version

Verify Fix Applied:

Verify firmware version is 2.29 or later after update. Test config file upload functionality.

📡 Detection & Monitoring

Log Indicators:

  • Unusual config file uploads
  • Failed authentication attempts to management interface
  • Unexpected system command execution logs

Network Indicators:

  • Unusual traffic patterns from network devices
  • Unexpected outbound connections from devices
  • Config file uploads to management interfaces

SIEM Query:

source="network_device" AND (event="config_upload" OR event="command_execution")

🔗 References

📤 Share & Export