dbcve.org
Rg Uac 6000 Cc FirmwareOperating system · Ruijie

CVE-2024-4505

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, which was classified as critical, was found in Ruijie RG-UAC up to 20240428. This affects an unknown part of the file /view/IPV6/ipv6Addr/ip_addr_add_commit.php. The manipulation of the argument prelen/ethname 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-263109 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

OS command injection vulnerability in Ruijie RG-UAC Unified Access Control appliance. The ipv6Addr configuration endpoint /view/IPV6/ipv6Addr/ip_addr_add_commit.php fails to properly sanitize the prelen and ethname parameters, allowing remote attackers to inject arbitrary OS commands via the argument values. The vulnerability is remotely exploitable and public exploits exist.

MitigationRestrict network access to the administrative interface, implement WAF rules to detect and block command injection patterns in the prelen/ethname parameters, or replace the device since the vendor has not responded to disclosures.

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 device administrative interface or check the device label/hardware to confirm it is a Ruijie RG-UAC Unified Access Control appliance. Look for model numbers such as RG-UAC 6000 CC, 6000 E10, 6000 E10c, 6000 E20, 6000 E20c, 6000 E20m, 6000 E50, or 6000 E50c.
    Affected if The device is any Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c). All versions of these models are affected.
  2. Check if IPv6 configuration feature is enabled
    Log into the administrative web interface and navigate to the IPv6 configuration section, typically under Network Settings or similar. Look for IPv6 address configuration options or the ipv6Addr module.
    Affected if The IPv6 address configuration feature (ipv6Addr) is accessible or enabled on the device.
  3. Verify the vulnerable endpoint exists
    Attempt to access the URL path /view/IPV6/ipv6Addr/ip_addr_add_commit.php on the device through the web interface. This may require authentication.
    Affected if The endpoint /view/IPV6/ipv6Addr/ip_addr_add_commit.php returns a valid response (rather than a 404 error), indicating the ipv6Addr module is present.
  4. Confirm network accessibility of admin interface
    Determine if the device administrative interface is exposed to network access. Check firewall rules, ACLs, or network segmentation surrounding the device.
    Affected if The device administrative web interface (port 80/443 or the device IP) is reachable from network segments other than a trusted management network.

If the device is a Ruijie RG-UAC 6000 series appliance (any version) with the IPv6 address configuration feature accessible, and the administrative interface is network-accessible, then the environment is affected by CVE-2024-4505.

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

Restrict network access to the administrative interface, implement WAF rules to detect and block command injection patterns in the prelen/ethname parameters, or replace the device since the vendor has not responded to disclosures.

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-4505 — 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-4505 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