CVE-2024-5337
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 and classified as critical. This issue affects some unknown processing of the file /view/systemConfig/sys_user/user_commit.php. The manipulation of the argument email2/user_name 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-266243. 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 confidenceA command injection vulnerability exists in Ruijie RG-UAC's user_commit.php file. Attackers can inject OS commands through the email2 and user_name parameters due to insufficient input sanitization. This remote, high-severity flaw allows arbitrary command execution on the underlying system.
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 product is deployedCheck system information, web interface banner, or network device inventory to identify the device model as one of the listed RG-UAC 6000 series (C, E10, E10c, E20, E20c, E20m, E50, E50c)Affected if The device is identified as any Ruijie RG-UAC 6000 series model from the affected list
-
Verify user_commit.php exists on the web serverAttempt to access the path /user_commit.php (or the full path if known for this product) via HTTP/HTTPS request and check for a 200 response or file presence via file system access if availableAffected if The user_commit.php file is present and accessible via web request
-
Check if the vulnerable parameters are acceptedSubmit a test HTTP POST or GET request to the user_commit.php endpoint including the email2 and/or user_name parameters with benign test values, observe if the application accepts and processes these parametersAffected if The email2 and user_name parameters are accepted and processed by the application without validation errors
-
Verify the application processes user input in system callsIf accessible, review the user_commit.php source code or observe application behavior when special characters are submitted in the email2 or user_name parameters to determine if unsanitized input reaches system command executionAffected if User input from email2 or user_name parameters is passed to shell execution functions without proper sanitization
If the environment contains a Ruijie RG-UAC 6000 series device and the user_commit.php endpoint is accessible with unvalidated email2 or user_name parameters, the environment is affected by CVE-2024-5337.
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 dataImplement strict input validation and sanitization on all user-supplied parameters, particularly email2 and user_name. Replace any unsafe shell command execution with parameterized functions or safe APIs that do not pass user input to system shells.
- 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-5337 — 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-5337 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