CVE-2024-5339
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 declared as critical. Affected by this vulnerability is an unknown functionality of the file /view/vpn/autovpn/online_check.php. The manipulation of the argument peernode leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-266245 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 confidenceOS command injection vulnerability in Ruijie RG-UAC's /view/vpn/autovpn/online_check.php file. The peernode parameter is not properly sanitized, allowing remote attackers to execute arbitrary OS commands. Public exploit available; vendor did not respond to disclosure.
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 model is Ruijie RG-UAC 6000 seriesAccess the device management interface or check system information pages to identify if the device is a Ruijie RG-UAC model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c)Affected if The device is any Ruijie RG-UAC 6000 series model listed in the affected products
-
Check firmware versionLocate the firmware version information in the device admin panel or system settings. Compare against the affected version listAffected if Any firmware version is present, as all versions of the listed models are affected
-
Verify the vulnerable PHP file existsCheck if the file /view/vpn/autovpn/online_check.php is present on the web server by attempting to access it via HTTP/HTTPSAffected if The file exists and is accessible via the web interface
-
Test for command injection via peernode parameterSend an HTTP request to /view/vpn/autovpn/online_check.php with a test payload in the peernode parameter (e.g., adding a recognizable ping or DNS lookup to confirm injection)Affected if The parameter executes OS commands instead of treating input as a literal value, confirming the vulnerability is present
The environment is affected if the device is a Ruijie RG-UAC 6000 series model (CC, E10, E10c, E20, E20c, E20m, E50, or E50c) and the vulnerable endpoint /view/vpn/autovpn/online_check.php is accessible and processes the peernode parameter without sanitization.
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 dataIf vendor patch unavailable, restrict network access to the management interface via firewall/ACLs, implement WAF rules to block command injection patterns, and monitor for IOCs. Consider isolating the device or replacing if unpatched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5339 — 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-5339 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