CVE-2024-5338
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 20240516. It has been classified as critical. Affected is an unknown function of the file /view/vpn/autovpn/online.php. The manipulation of the argument peernode leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-266244. 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 device. The peernode parameter in /view/vpn/autovpn/online.php is not properly sanitized before being passed to a system call, allowing remote attackers to execute arbitrary operating system commands. Public exploit available, increasing immediate risk.
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.
-
Identify the device modelAccess the device admin interface or check device documentation/label to confirm it is a Ruijie RG-UAC model from the affected list: 6000 CC, 6000 E10, 6000 E10c, 6000 E20, 6000 E20c, 6000 E20m, 6000 E50, or 6000 E50cAffected if The device matches any of these models (all versions are affected)
-
Confirm the web interface is exposedVerify that the Ruijie RG-UAC web management interface is accessible over the network on the default HTTP/HTTPS portsAffected if The web interface is reachable from network segments where untrusted users could access it
-
Check if the vulnerable endpoint existsAttempt to access /view/vpn/autovpn/online.php on the device or examine the web server configuration for this pathAffected if The endpoint exists and responds to requests (indicates the VPN autovpn module is installed)
-
Determine if the autovpn feature is enabledCheck the device VPN configuration settings to see if the autovpn feature is configured or enabledAffected if The autovpn feature is active - the command injection only affects this feature when it is in use
-
Inspect for indicators of compromiseReview web server access logs and system logs for unusual requests to /view/vpn/autovpn/online.php with unexpected characters (such as semicolons, pipes, or command syntax) in the peernode parameterAffected if Log analysis reveals suspicious requests containing command injection patterns or unexpected system command executions
A user is affected if they operate any Ruijie RG-UAC model from the affected list (6000 series) with the web interface accessible and the autovpn module present, regardless of version since all versions are vulnerable.
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 dataImmediately restrict network access to the affected /view/vpn/autovpn/online.php endpoint, implement input validation/WAF rules to block malicious payloads in the peernode parameter, and monitor for Indicators of Compromise. If the VPN autovpn feature is not critical, consider disabling it until an official vendor patch is released.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5338 — 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-5338 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