dbcve.org
Rg Uac 6000 E20c FirmwareOperating system · Ruijie

CVE-2024-5340

HIGH · 7.2 CVSS v3.1 Published 2024-05-25
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 20240516. It has been rated as critical. Affected by this issue is some unknown functionality of the file /view/vpn/autovpn/sub_commit.php. The manipulation of the argument key leads to os command injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-266246 is the identifier 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 access control devices. The flaw is in the /view/vpn/autovpn/sub_commit.php endpoint where the 'key' parameter is not properly sanitized before being passed to system commands, allowing remote attackers to execute arbitrary OS commands.

MitigationSince the vendor did not respond and no patch exists, immediate mitigation requires network segmentation to restrict exposure, deployment of WAF rules to block malicious command injection payloads in the key parameter, and disabling the autovpn functionality if not business-critical.

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 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
Rg Uac 6000 E50m FirmwareOperating system
Affected:all versions
Rg Uac 6000 Ea FirmwareOperating system
Affected:all versions
Rg Uac 6000 Ei FirmwareOperating system
Affected:all versions
Rg Uac 6000 Isg02 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
    Check the device label, web interface header, or SNMP sysDescr for 'RG-UAC' or Ruijie model number (E20c, E20m, E50, E50c, E50m, EA, EI, ISG02)
    Affected if The device is any of the listed Ruijie RG-UAC 6000 series models
  2. Verify firmware version is in affected range
    Access the device web interface (typically via HTTPS on port 443 or 8443), navigate to System > Firmware/About, or run 'show version' via CLI if SNMP or console is available
    Affected if The device is running any firmware version on the RG-UAC 6000 E20c, E20m, E50, E50c, E50m, EA, EI, or ISG02 models (all versions are affected)
  3. Confirm the autovpn feature is accessible
    Attempt to access the URL path /view/vpn/autovpn/sub_commit.php on the device's web server (for example: https://<device-ip>/view/vpn/autovpn/sub_commit.php)
    Affected if The endpoint responds (even with an error), indicating the vulnerable PHP script exists on the device
  4. Check if autovpn is enabled
    Log into the device web interface and navigate to VPN > AutoVPN or examine the configuration file for 'autovpn' or 'sub_commit' settings via CLI (show running-config | include autovpn)
    Affected if The autovpn functionality is enabled or the sub_commit.php endpoint is reachable over the network

If the device is a Ruijie RG-UAC 6000 series model (E20c, E20m, E50, E50c, E50m, EA, EI, or ISG02) and the /view/vpn/autovpn/sub_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

Since the vendor did not respond and no patch exists, immediate mitigation requires network segmentation to restrict exposure, deployment of WAF rules to block malicious command injection payloads in the key parameter, and disabling the autovpn functionality if not business-critical.

Fix this in Rg Uac 6000 E20c Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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