CVE-2024-4814
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 classified as critical was found in Ruijie RG-UAC up to 20240506. Affected by this vulnerability is an unknown functionality of the file /view/networkConfig/RouteConfig/StaticRoute/static_route_edit_commit.php. The manipulation of the argument oldipmask/oldgateway leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-263935. 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 controller's static route configuration (static_route_edit_commit.php). The oldipmask and oldgateway parameters are not properly sanitized before being passed to system shell commands, allowing remote attackers to execute arbitrary OS commands by injecting shell metacharacters.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if the target is a Ruijie RG-UAC unified access controllerAccess the device management interface or check the system information page. Look for product name/model information (RG-UAC 6000 series) in the web interface header, login page, or system status page.Affected if The device is a Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c)
-
Verify the static route management interface is accessibleAttempt to access the static route configuration page in the web management interface. Common paths include /static_route_edit_commit.php or navigate through Network > Routing > Static Route in the management console.Affected if The static route configuration page loads and accepts input for oldipmask and oldgateway parameters
-
Check for the vulnerable PHP file presenceSend an HTTP GET request to the path /static_route_edit_commit.php on the web server. Check if the file exists and returns a valid HTTP response (200 OK) rather than a 404 error.Affected if The file returns a 200 OK response, indicating the vulnerable endpoint is present on the device
-
Confirm network accessibility of the management interfaceVerify that the RG-UAC web management interface (typically ports 80 or 443) is reachable from the network segment being assessed. Use telnet, curl, or a browser to confirm HTTP/HTTPS access.Affected if The management interface is exposed on the network and accepts connections
If the device is a Ruijie RG-UAC 6000 series and the static_route_edit_commit.php endpoint is accessible, the environment is affected by this vulnerability since all firmware versions for these models are impacted.
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 dataRestrict network access to the RG-UAC management interface, implement WAF rules to detect and block command injection attempts in oldipmask/oldgateway parameters, and disable or restrict the static route management functionality until an official vendor patch is released.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4814 — 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-4814 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