dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4508

HIGH · 7.2 CVSS v3.1 Published 2024-05-06
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
A vulnerability was found in Ruijie RG-UAC up to 20240428. It has been classified as critical. Affected is an unknown function of the file /view/IPV6/ipv6StaticRoute/static_route_edit_ipv6.php. The manipulation of the argument oldipmask/oldgateway/olddevname leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-263112. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

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

OS command injection vulnerability in Ruijie RG-UAC unified access controller. The IPv6 static route edit page (/view/IPV6/ipv6StaticRoute/static_route_edit_ipv6.php) fails to sanitize user-supplied input in the oldipmask, oldgateway, and olddevname parameters before passing them to system shell commands, allowing remote attackers to execute arbitrary OS commands.

MitigationImplement strict input validation and sanitization for all route parameters before shell execution; ideally migrate to parameterized APIs or safe command builders that avoid shell invocation entirely.

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
Rg Uac 6000 Cc FirmwareOperating system
Affected:all versions
Rg Uac 6000 E10 FirmwareOperating system
Affected:all versions
Rg Uac 6000 E10c FirmwareOperating system
Affected:all versions
Rg Uac 6000 E20 FirmwareOperating system
Affected:all versions
Rg Uac 6000 E20c FirmwareOperating system
Affected:all versions
Rg Uac 6000 E20m FirmwareOperating system
Affected:all versions
Rg Uac 6000 E50 FirmwareOperating system
Affected:all versions
Rg Uac 6000 E50c FirmwareOperating system
Affected:all versions

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 installed product
    Access the device administrative interface or check system information to confirm the device is a Ruijie RG-UAC unified access controller. Look for model identifiers such as RG-UAC 6000 CC, E10, E10c, E20, E20c, E20m, E50, or E50c in the device status or firmware information page.
    Affected if The device is a Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c)
  2. Verify IPv6 routing feature is accessible
    Log into the RG-UAC administrative interface and navigate to the IPv6 static route configuration page. The vulnerable path is typically found under Network Settings or Routing sections. Attempt to access the URL path /view/IPV6/ipv6StaticRoute/static_route_edit_ipv6.php or locate the equivalent page in the web interface navigation.
    Affected if The IPv6 static route editing functionality is present and accessible in the administrative interface
  3. Check if the vulnerable script is present
    Using authenticated access to the device (via web interface or administrative shell), verify that the PHP script static_route_edit_ipv6.php exists in the /view/IPV6/ipv6StaticRoute/ directory on the device filesystem.
    Affected if The file static_route_edit_ipv6.php exists in the expected path on the device
  4. Confirm the device is reachable over network
    Verify the RG-UAC web management interface is network-accessible (typically on ports 80 or 443). The vulnerability is exploitable remotely, so any exposed management interface with the IPv6 routing feature constitutes the attack surface.
    Affected if The device administrative interface is accessible from network locations and IPv6 routing features are enabled

The environment is affected if it consists of any Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c) with the IPv6 static route editing functionality accessible via the web interface.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for all route parameters before shell execution; ideally migrate to parameterized APIs or safe command builders that avoid shell invocation entirely.

Fix this in Rg Uac 6000 Cc Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4508 — 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-4508 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