CVE-2024-36475
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFutureNet NXR series, VXR series and WXR series provided by Century Systems Co., Ltd. contain an active debug code vulnerability. If a user who knows how to use the debug function logs in to the product, the debug function may be used and an arbitrary OS command may be executed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAuthenticated command injection vulnerability in the debug function of Century Systems FutureNet NXR, VXR, and WXR series routers. A user with knowledge of the debug function can execute arbitrary OS commands after logging in.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.4.10all versions< 21.14.11c< 21.12.10< 21.15.6< 6.23.11< 21.7.32< 21.15.2cCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router model and seriesAccess router CLI or web interface and locate the model identification (NXR 1300, NXR 155/c, NXR 610x, NXR G050, NXR G060, NXR G100, NXR G110, NXR G120, or VXR/WXR series). Confirm it is a Century Systems FutureNet router.Affected if Model is any NXR, VXR, or WXR series from Century Systems
-
Check firmware version against affected rangesUse the router CLI command to display firmware version (typically 'show version' or 'system status' in the CLI). Compare against the affected version thresholds for your specific model.Affected if Firmware version is below the safe threshold for your model: NXR 1300 < 7.4.10, NXR 610x < 21.14.11c, NXR G050 < 21.12.10, NXR G060 < 21.15.6, NXR G100 < 6.23.11, NXR G110 < 21.7.32, NXR G120 < 21.15.2c, or NXR 155/c any version
-
Verify if debug function is accessibleCheck if the debug command or debug function is available in the router CLI or web interface. Look for debug-related menu options, commands starting with 'debug', or diagnostic interfaces.Affected if Debug function is present and accessible to authenticated users
-
Confirm authentication method for debug accessReview user accounts and privileges configured on the router. Determine if standard user accounts can access debug functionality after login.Affected if Authenticated users (including standard non-admin accounts) can access debug features
Your environment is affected if you run an Century Systems FutureNet NXR/VXR/WXR router with firmware below the safe version threshold for your model and the debug function remains accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.23.117.4.1021.7.32
Contact Century Systems for firmware updates that disable debug code in production releases, and implement network segmentation to restrict access to debug interfaces.
Upgrade to NXR 1300 firmware >= 7.4.10, NXR 610x >= 21.14.11c, NXR G050 >= 21.12.10, NXR G060 >= 21.15.6, NXR G100 >= 6.23.11, NXR G110 >= 21.7.32, NXR G120 >= 21.15.2c (contact vendor for NXR 155/c)
- 1. Identify the exact model number of your FutureNet NXR device from the affected product list (NXR 1300, 155/c, 610x, G050, G060, G100, G110, or G120)
- 2. Check the current firmware version installed on the device through the admin interface or CLI
- 3. Download the corresponding fixed firmware version from Century Systems official website or support portal: https://www.centurysys.co.jp/
- 4. For NXR 155/c: Contact Century Systems directly as all versions are affected and no fixed version is specified in the advisory
- 5. Backup the current device configuration before upgrading
- 6. Upload and install the fixed firmware version via the device's web interface or CLI following the vendor's upgrade instructions
- 7. After upgrade, verify the new firmware version matches or exceeds the minimum fixed version for your model
- 8. Change default/admin passwords and disable debug functionality if not needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36475 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data