☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
SOON 🐛 CWE-489
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-36475

CVE-2024-36475 Privilege Escalation in Century systems co., ltd.
📅 PUBLISHED: 2024-07-17 08:48 UTC 🔄 UPDATED: 2026-08-12 08:59 UTC
⏳ SCORE PENDING — ANALYSIS IN PROGRESS [ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.51%
👁️
0.51% probability
12.7× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1204
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: UNKNOWN / CHECK VENDOR
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
SOON
PENDING NVD
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-36475 identifies an active debug code vulnerability in Century Systems Co., Ltd.'s FutureNet NXR, VXR, and WXR series routers. The vulnerability allows an authenticated user who knows how to invoke the debug function to execute arbitrary OS commands on the device. This is a classic case of a debug backdoor left in production firmware, enabling privilege escalation and full device compromise. The vendor has not released a patch, and no public proof-of-concept (PoC) or exploit code is available at this time.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

CVSS Breakdown & Threat Level

CVSS Score: 0.0 (No vector assigned by NVD) Threat Level: High (based on impact) Attack Vector: Local (requires authenticated access) Attack Complexity: Low Privileges Required: Low (user-level) User Interaction: None Scope: Unchanged Confidentiality Impact: High Integrity Impact: High Availability Impact: High

Deep Dive & Mechanics

The vulnerability resides in the debug functionality of the affected router series. The firmware includes a debug mode that is not intended for production use. An attacker who gains access to the device (e.g., via default credentials, weak passwords, or other means) can activate this debug mode. Once activated, the debug interface allows the execution of arbitrary OS commands with root privileges.

The debug code is likely a leftover from development or testing phases. It may be triggered via a specific HTTP request, a hidden CLI command, or a special sequence of inputs. The exact trigger mechanism is not publicly documented, but the advisory confirms that knowledge of the debug function is sufficient to exploit it.

Vulnerable vs. Patched Code

Vulnerable Code (Hypothetical):

// Debug function exposed in production
void debug_exec(char *cmd) {
    system(cmd); // No authentication or sanitization
}

Patched Code (Hypothetical):

// Debug function removed or disabled
// No debug_exec function present in production firmware

Since no patch is available, the only mitigation is to disable debug functionality or restrict access to the device.

Exploitation & Lab Setup

Red Team

  1. Reconnaissance: Identify FutureNet routers on the network using Shodan or Nmap.
    nmap -p 80,443,22 --open 192.168.1.0/24
    
  2. Access: Gain authenticated access via default credentials (e.g., admin/admin) or brute-force.
  3. Trigger Debug: Send a crafted HTTP request or CLI command to activate debug mode.
    # Example HTTP request (hypothetical)
    curl -X POST http://192.168.1.1/debug -d "cmd=id"
    
  4. Execute Command: Run arbitrary OS commands.
    # Example command execution
    curl -X POST http://192.168.1.1/debug -d "cmd=cat /etc/shadow"
    

Blue Team

  1. Monitor Logs: Check for unusual HTTP requests to /debug or similar endpoints.
  2. Network Segmentation: Isolate router management interfaces from untrusted networks.
  3. Access Control: Enforce strong passwords and disable default accounts.
  4. Firmware Updates: Monitor vendor for patches; if none, consider replacing the device.

Indicators of Compromise (IOCs)

  • Network: HTTP requests to /debug, /shell, or similar endpoints.
  • Process: Unusual processes like bash, sh, or python spawned by the web server.
  • File: Presence of debug scripts or binaries in /tmp or /var.
  • Log: Entries in system logs showing debug or exec commands.

Detection Engineering

YARA Rule

rule CVE_2024_36475_Debug_Code {
    meta:
        description = "Detects debug code in FutureNet router firmware"
        author = "Valters IT"
        date = "2025-04-01"
        reference = "CVE-2024-36475"
    strings:
        $debug_func = "debug_exec" nocase
        $debug_trigger = "debug_mode" nocase
    condition:
        any of them
}

Sigma Rule

title: FutureNet Router Debug Code Exploitation
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects attempts to exploit CVE-2024-36475 debug code vulnerability
author: Valters IT
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: 'POST'
        cs-uri-stem: '/debug'
    condition: selection
falsepositives:
    - Legitimate debug usage (unlikely)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2024-36475 FutureNet Router Debug Code Exploitation"; flow:to_server; content:"POST"; http_method; content:"/debug"; http_uri; classtype:attempted-admin; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate: Disable debug functionality if possible via configuration.
  2. Short-term: Restrict management access to trusted IPs only.
  3. Long-term: Replace affected devices with patched or alternative hardware.
  4. Monitoring: Implement detection rules (YARA, Sigma, Suricata) to identify exploitation attempts.
  5. Vendor Contact: Pressure Century Systems to release a firmware patch.

Valters IT
Securing Digital Frontiers

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

FutureNet NXR
FutureNet VXR
FutureNet WXR

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-36475/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.