dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4509

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 declared as critical. Affected by this vulnerability is an unknown functionality of the file /view/IPV6/naborTable/add_commit.php. The manipulation of the argument ip_addr/mac_addr leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-263113 was assigned to this vulnerability. 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 add_commit.php file in the IPV6 naborTable functionality accepts user-supplied ip_addr or mac_addr parameters and passes them unsanitized to system shell commands, allowing remote attackers to execute arbitrary OS commands.

MitigationImplement strict input validation using allowlists for IP and MAC address formats, and replace any system call execution with parameterized alternatives or safe API functions that do not invoke shell interpreters.

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. Confirm device model
    Access the device's web management interface or check system information pages to identify the exact RG-UAC model number (such as RG-UAC 6000 CC, E10, E10c, E20, E20c, E20m, E50, or E50c).
    Affected if The device is any of the listed Ruijie RG-UAC 6000 series models.
  2. Verify firmware version
    Navigate to the device's web interface system settings or use CLI commands (such as 'show version' or 'display device') to retrieve the installed firmware version.
    Affected if The firmware version matches any of the affected models (all versions of the listed models are vulnerable).
  3. Check web interface accessibility
    Attempt to access the device's web management interface via HTTP/HTTPS on the typical management ports (commonly port 80 or 443).
    Affected if The web interface is accessible, indicating the PHP application is running and the vulnerable code is present.
  4. Locate vulnerable PHP file
    Check for the presence of the add_commit.php file in the web root or related directories. This file is typically found in paths related to IPv6 functionality.
    Affected if The file add_commit.php exists on the device's web server.
  5. Verify IPv6 neighbor table feature
    Access or probe the IPv6 naborTable functionality within the web interface to confirm the feature is enabled and accessible.
    Affected if The IPv6 neighbor table (naborTable) feature is enabled and accessible through the web interface, exposing the vulnerable parameters ip_addr and mac_addr.

If the device is a Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c) with an accessible web interface and the IPv6 neighbor table feature is enabled, the environment is affected by this vulnerability.

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 using allowlists for IP and MAC address formats, and replace any system call execution with parameterized alternatives or safe API functions that do not invoke shell interpreters.

Fix this in Rg Uac 6000 Cc Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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