dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4501

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 was found in Ruijie RG-UAC up to 20240428. It has been rated as critical. This issue affects some unknown processing of the file /view/bugSolve/captureData/commit.php. The manipulation of the argument tcpDump leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-263105 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 unified threat management appliances. The flaw is in the /view/bugSolve/captureData/commit.php script where the 'tcpDump' parameter is passed unsafely to system shell commands, allowing remote attackers to execute arbitrary operating system commands.

MitigationImmediately restrict network access to the affected Ruijie RG-UAC management interface. If possible, disable or restrict the vulnerable captureData functionality pending a vendor patch. Implement web application firewall rules to detect and block command injection payloads in the tcpDump parameter.

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 RG-UAC model
    Access the device management interface or check the device label/firmware to confirm the exact model number (6000 CC, E10, E10c, E20, E20c, E20m, E50, or E50c)
    Affected if The device model is any of the Ruijie RG-UAC 6000 series listed in the affected products
  2. Confirm firmware version
    Navigate to the device web interface System Settings or use CLI command 'show version' to retrieve the installed firmware version
    Affected if Any firmware version is installed on an affected RG-UAC 6000 model (all versions are vulnerable)
  3. Verify vulnerable web path exists
    Check if the file /view/bugSolve/captureData/commit.php exists on the web server by attempting to access it via HTTP/HTTPS or examining the web root directory structure
    Affected if The commit.php script exists in the /view/bugSolve/captureData/ directory
  4. Confirm tcpDump parameter handling
    Inspect the commit.php source code to verify the tcpDump parameter is passed directly to shell_exec, exec, or similar PHP functions without sanitization
    Affected if The tcpDump parameter is used in a system call without proper input validation
  5. Check captureData functionality status
    Review the device configuration to determine if the captureData feature is enabled and accessible
    Affected if The captureData functionality is enabled and exposed to network users

If the device is a Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c) and the /view/bugSolve/captureData/commit.php endpoint is accessible, the environment is affected by this command injection 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

Immediately restrict network access to the affected Ruijie RG-UAC management interface. If possible, disable or restrict the vulnerable captureData functionality pending a vendor patch. Implement web application firewall rules to detect and block command injection payloads in the tcpDump parameter.

Fix this in Rg Uac 6000 Cc Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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