dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4816

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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, which was classified as critical, was found in Ruijie RG-UAC up to 20240506. This affects an unknown part of the file /view/networkConfig/GRE/gre_add_commit.php. The manipulation of the argument name/remote/local/IP leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-263937 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

A critical OS command injection vulnerability exists in Ruijie RG-UAC devices in the GRE tunnel configuration file (gre_add_commit.php). The name, remote, local, and IP parameters are not properly sanitized before being passed to system commands, allowing unauthenticated remote attackers to execute arbitrary operating system commands.

MitigationSince no vendor patch is available, implement web application firewall rules to block malicious input patterns on the affected endpoint, disable the vulnerable GRE configuration feature if not needed, or implement network segmentation to restrict access to the management interface.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 device model and firmware version
    Access the device web interface or use SNMP/SSH to retrieve the system model and firmware version. Look for RG-UAC 6000 followed by a variant suffix (CC, E10, E10c, E20, E20c, E20m, E50, or E50c).
    Affected if The device is a Ruijie RG-UAC 6000 series model (any variant) running any firmware version.
  2. Confirm the device web management interface is accessible
    Attempt to reach the device HTTP/HTTPS management interface over the network. Check if the login page or any Ruijie RG-UAC web portal responds.
    Affected if The web interface is reachable from an attacker-controlled network segment.
  3. Verify the GRE tunnel configuration feature exists
    Navigate through the device web interface to locate the GRE tunnel configuration section. This is typically found under Network Settings, Tunnel Settings, or similar menu paths depending on the firmware version.
    Affected if The GRE tunnel configuration feature is present and accessible in the web interface.
  4. Check for the vulnerable gre_add_commit.php endpoint
    Attempt to access the URI path /gre_add_commit.php directly via HTTP or HTTPS request to the device.
    Affected if The gre_add_commit.php endpoint returns any response (including error messages) indicating the script exists.
  5. Assess network exposure of the management interface
    Review firewall rules, ACLs, or network segmentation configurations to determine if the device management interface is exposed to untrusted networks or the internet.
    Affected if The management interface is accessible from untrusted networks without adequate access controls.

A user is affected if they operate any Ruijie RG-UAC 6000 series device (CC, E10, E10c, E20, E20c, E20m, E50, E50c) with the web management interface accessible on the network, as all firmware versions contain the command injection flaw in the GRE tunnel configuration script.

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

Since no vendor patch is available, implement web application firewall rules to block malicious input patterns on the affected endpoint, disable the vulnerable GRE configuration feature if not needed, or implement network segmentation to restrict access to the management interface.

Fix this in Rg Uac 6000 Cc Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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