dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4503

HIGH · 7.2 CVSS v3.1 Published 2024-05-05
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 classified as critical was found in Ruijie RG-UAC up to 20240428. Affected by this vulnerability is an unknown functionality of the file /view/dhcp/dhcpConfig/dhcp_relay_commit.php. The manipulation of the argument interface_from leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-263107. 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 Control allows remote attackers to execute arbitrary OS commands via the interface_from parameter in the dhcp_relay_commit.php file. The lack of input sanitization in the DHCP relay configuration functionality enables attackers to inject shell commands that are executed with web server privileges.

MitigationSince the vendor has not responded to disclosures, organizations should immediately restrict access to the affected management interface from untrusted networks, deploy WAF rules to detect and block command injection patterns in the interface_from parameter, and consider network segmentation or alternative solutions while awaiting an official patch.

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 device model
    Access the device web interface or CLI and check the system information or model number. Look for RG-UAC 6000 series identifiers (CC, E10, E10c, E20, E20c, E20m, E50, E50c).
    Affected if The device is any Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c).
  2. Verify firmware version
    Check the device firmware version through the web UI (typically under System > Device Info or System > License) or via CLI command 'show version'.
    Affected if The device runs any firmware version on the RG-UAC 6000 series - all versions of the listed models are affected.
  3. Confirm DHCP relay is configured
    Access the web interface and navigate to Network Settings > DHCP Relay or similar path. Check if DHCP relay feature is enabled and configured with an interface_from parameter.
    Affected if DHCP relay functionality is enabled and the interface_from parameter is present in the configuration.
  4. Check web interface accessibility
    Verify if the Ruijie RG-UAC web management interface (typically ports 443 or 8080) is accessible from network segments. Review firewall or ACL rules controlling access to the device management IP.
    Affected if The web management interface is exposed to untrusted networks or the internet.
  5. Inspect DHCP relay configuration file
    Locate and examine the dhcp_relay_commit.php file on the device filesystem (typically under /www or /webui directory). Check for unsanitized use of the interface_from parameter in system/exec calls.
    Affected if The dhcp_relay_commit.php file exists and processes the interface_from parameter without input sanitization.

You are affected if you are running any Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c) with the DHCP relay feature enabled and the web management interface exposed.

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 the vendor has not responded to disclosures, organizations should immediately restrict access to the affected management interface from untrusted networks, deploy WAF rules to detect and block command injection patterns in the interface_from parameter, and consider network segmentation or alternative solutions while awaiting an official patch.

Fix this in Rg Uac 6000 Cc Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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