CVE-2024-4507
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 · uneditedA vulnerability was found in Ruijie RG-UAC up to 20240428 and classified as critical. This issue affects some unknown processing of the file /view/IPV6/ipv6StaticRoute/static_route_add_ipv6.php. The manipulation of the argument text_prefixlen/text_gateway/devname leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-263111. 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 confidenceOS command injection vulnerability in Ruijie RG-UAC unified access control device. The ipv6StaticRoute functionality in static_route_add_ipv6.php passes user-supplied parameters (text_prefixlen, text_gateway, devname) directly to system shell commands without sanitization, allowing arbitrary OS command execution. Attack is remote and a public exploit exists.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is Ruijie RG-UACAccess the device web interface or check system information via CLI (show system-info or similar vendor command). Look for model number indicating RG-UAC 6000 series (CC, E10, E10c, E20, E20c, E20m, E50, E50c).Affected if Device is a Ruijie RG-UAC 6000 series model and the ipv6StaticRoute feature is accessible or has been accessed.
-
Identify firmware versionCheck the device firmware version through web interface (usually under System > Firmware or System > Version) or via CLI command like 'show version' or 'get system info'.Affected if Firmware version is any version on the affected models (all versions of the listed models are affected).
-
Verify IPv6 static route functionality is presentNavigate to the static routing configuration page in the web interface, specifically look for IPv6 static route settings (static_route_add_ipv6.php). Check if the file exists on the device filesystem via CLI access if available.Affected if The static_route_add_ipv6.php file exists and the IPv6 static route configuration interface is accessible or was previously configured.
-
Check for unauthorized commands or scriptsReview device logs, especially web access logs and system command logs. Look for unusual commands, unexpected network connections, or suspicious processes. Search for indicators like shell metacharacters (; | & $`) in HTTP request logs targeting the static route pages.Affected if Logs show command injection patterns (shell metacharacters) in requests to static_route_add_ipv6.php, or unexpected commands have been executed on the system.
-
Inspect for backdoors or persistenceCheck for new user accounts, scheduled tasks, cron jobs, or startup scripts that may have been created. Review /etc/passwd, /etc/crontab, and startup configuration files if CLI access is available.Affected if Unauthorized accounts, scripts, or scheduled tasks exist on the device that were not configured by the administrator.
A user is affected if they operate a Ruijie RG-UAC 6000 series device (any firmware version) with the IPv6 static route functionality exposed, particularly if the device is directly accessible from network or has been targeted by remote attacks.
Generated from the published advisory. Verify against your own configuration.
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 dataSince vendor did not respond and no patch is available, implement network segmentation to isolate the device, deploy WAF rules to detect/block command injection patterns in HTTP parameters, and monitor for indicators of compromise. Consider disabling IPv6 static route functionality if not required.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4507 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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