CVE-2024-5336
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 has been found in Ruijie RG-UAC up to 20240516 and classified as critical. This vulnerability affects the function addVlan of the file /view/networkConfig/vlan/vlan_add_commit.php. The manipulation of the argument phyport leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-266242 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 confidenceOS command injection vulnerability in Ruijie RG-UAC unified threat management appliance. The addVlan function in vlan_add_commit.php does not properly sanitize the phyport parameter before passing it to an operating system command, allowing remote authenticated attackers (or potentially unauthenticated if the interface is exposed) to execute arbitrary OS commands.
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 Ruijie RG-UAC 6000 series applianceAccess the device management console or check the product model via 'show system info' or the web interface login page. Look for model numbers: RG-UAC 6000 CC, E10, E10c, E20, E20c, E20m, E50, or E50c.Affected if The device is a Ruijie RG-UAC 6000 series model (any variant listed in the affected products).
-
Identify firmware versionLog into the RG-UAC web interface or CLI and navigate to System Settings > Firmware Version, or run 'show version' command via console/SSH. Compare the firmware version against the affected range.Affected if Any firmware version is installed, as all versions of the listed models are affected.
-
Verify web interface network exposureCheck the device network configuration to determine if the management web interface (ports 80/443 or custom HTTPS port) is bound to an interface accessible from untrusted networks. Use 'show ip interface' or review firewall rules.Affected if The web management interface is accessible from WAN/untrusted networks without IP restriction.
-
Confirm VLAN management feature accessibilityAttempt to access the VLAN configuration page in the web interface (typically under Network > VLAN or similar path). Check if vlan_add_commit.php is reachable via the web server.Affected if The VLAN management feature is enabled and accessible to the attacker (authenticated session or unauthenticated if interface is exposed).
-
Audit for indicators of compromiseReview system logs (/var/log/messages or device logs via web) for suspicious shell commands, unexpected cron jobs, or unauthorized admin accounts. Check for unexpected processes or network connections using 'top' or 'netstat'.Affected if Suspicious shell commands appear in logs, unexpected processes are running, or unauthorized administrative accounts exist.
If the device is a Ruijie RG-UAC 6000 series model with any firmware version and its management interface is accessible (especially from untrusted networks), the environment is potentially affected by CVE-2024-5336.
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 to trusted IPs only. If the interface must remain exposed, implement WAF rules to detect and block command injection patterns in the phyport parameter. Contact Ruijie for official patch; escalate through support channels or consider compensating controls until vendor addresses the issue.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5336 — 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-5336 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