dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4255

HIGH · 7.2 CVSS v3.1 Published 2024-04-27
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, which was classified as critical, has been found in Ruijie RG-UAC up to 20240419. This issue affects some unknown processing of the file /view/network Config/GRE/gre_edit_commit.php. The manipulation of the argument name 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-262145 was assigned to this vulnerability.

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 gre_edit_commit.php file in the GRE configuration module does not properly sanitize the 'name' parameter before passing it to an OS-level command, allowing remote authenticated attackers to execute arbitrary commands on the underlying operating system.

MitigationImmediately restrict network access to the RG-UAC management interface to only trusted admin IPs, and contact Ruijie for the official patch to remediate the command injection in the GRE configuration module.

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 device model
    Access the RG-UAC web interface or check the device label to confirm it is a Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c).
    Affected if The device is any Ruijie RG-UAC 6000 series model.
  2. Confirm firmware version
    Log into the RG-UAC management interface and navigate to System Status or About page to retrieve the firmware version. Compare against the known affected models.
    Affected if The device is running any firmware version on the RG-UAC 6000 series (all versions are affected).
  3. Verify GRE module is accessible
    Attempt to access the GRE configuration module in the RG-UAC web interface, typically found under Network Settings or VPN settings. Confirm the gre_edit_commit.php endpoint responds.
    Affected if The GRE configuration module is enabled and accessible via the web interface.
  4. Check for the vulnerable PHP file
    Inspect the web server filesystem for the presence of gre_edit_commit.php in the GRE configuration module directory.
    Affected if The file gre_edit_commit.php exists on the device.
  5. Review access logs for suspicious requests
    Examine HTTP access logs for the gre_edit_commit.php endpoint, looking for unusual parameter values in the 'name' field that may indicate exploitation attempts.
    Affected if There are log entries showing command injection payloads in requests to gre_edit_commit.php.

You are affected if your device is any Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c) running any firmware version, with the GRE configuration module accessible to authenticated users.

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 RG-UAC management interface to only trusted admin IPs, and contact Ruijie for the official patch to remediate the command injection in the GRE configuration module.

Fix this in Rg Uac 6000 Cc Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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