dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-11013

HIGH · 7.2 CVSS v3.1 Published 2024-11-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Command Injection vulnerability in NEC Corporation UNIVERGE IX from Ver9.2 to Ver10.10.21, for Ver10.8 up to Ver10.8.27, for Ver10.9 up to Ver10.9.14 and UNIVERGE IX-R/IX-V Ver1.2.15 and earlier allows a attacker to inject an arbitrary CLI commands to be executed on the device via the management interface.

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 confidence

Command injection vulnerability in NEC UNIVERGE IX and IX-R/IX-V routers allows attackers to inject and execute arbitrary CLI commands through the management interface. The vulnerability affects multiple version ranges from Ver9.2 through Ver10.10.21 (and earlier versions of 10.8, 10.9, and IX-R/IX-V), enabling full compromise of the network device.

MitigationUpdate affected devices to the latest patched firmware version. Until patched, restrict management interface access to trusted IP addresses or networks using ACLs, and disable remote management if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NEC UNIVERGE device model
    Access the router CLI or web interface and determine if the device is an IX, IX-R, or IX-V series router. Use commands such as 'show system' or check the web interface device information page.
    Affected if The device is any model in the IX, IX-R, or IX-V series families.
  2. Determine the installed firmware version
    Run the CLI command 'show version' or check the firmware version displayed in the router web interface under System or Device Information sections.
    Affected if The installed version falls within Ver9.2 through Ver10.10.21, or is an earlier version of 10.8 or 10.9, or is any version of the IX-R or IX-V series prior to patching.
  3. Verify management interface accessibility
    Check the router configuration for enabled management services using 'show ip http', 'show ip https', 'show telnet', or 'show ssh' commands. Review ACLs applied to management interfaces.
    Affected if The management interface (HTTP, HTTPS, Telnet, or SSH) is accessible from untrusted networks or the internet.
  4. Confirm remote management is enabled
    Examine the router configuration for remote management settings. Look for 'ip http server', 'ip https server', or 'management http/https' statements in the configuration.
    Affected if Remote management services are enabled on WAN or externally-facing interfaces without IP-based access restrictions.

A user is affected if they are running any NEC UNIVERGE IX, IX-R, or IX-V router with firmware versions from Ver9.2 through Ver10.10.21 (or earlier 10.8/10.9 versions) and the device management interface is accessible to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected devices to the latest patched firmware version. Until patched, restrict management interface access to trusted IP addresses or networks using ACLs, and disable remote management if not required.

Recommended fix Moderate confidence

UNIVERGE IX series: Ver10.10.22 or later; UNIVERGE IX-R/IX-V: Ver1.2.16 or later

  1. 1. Identify the current installed version of NEC UNIVERGE IX or UNIVERGE IX-R/IX-V by accessing the device management interface or using 'show version' command.
  2. 2. Based on the product line and current version, determine the minimum fixed version needed: For UNIVERGE IX series, upgrade to Ver10.10.22 or later; For UNIVERGE IX-R/IX-V, upgrade to Ver1.2.16 or later.
  3. 3. Download the firmware update from the official NEC support portal at jpn.nec.com or authorized NEC distribution channels.
  4. 4. Review the firmware upgrade procedure in the NEC UNIVERGE IX Configuration Guide to ensure proper steps are followed.
  5. 5. Backup the current device configuration before initiating the upgrade.
  6. 6. Upload the new firmware file through the device management interface or via TFTP/FTP as specified in the upgrade procedure.
  7. 7. Verify the upgrade was successful by confirming the new firmware version after reboot.
  8. 8. Validate that the command injection vulnerability is no longer present by testing management interface functionality.
Caveat Review NEC release notes for any configuration syntax changes or feature modifications between your current version and the target fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11013 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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