CVE-2024-4502
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 has been found in Ruijie RG-UAC up to 20240428. Affected is an unknown function of the file /view/dhcp/dhcpClient/dhcp_client_commit.php. The manipulation of the argument ifName 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. VDB-263106 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 Access Controller) allows remote attackers to execute arbitrary OS commands via the ifName parameter in /view/dhcp/dhcpClient/dhcp_client_commit.php. The lack of input sanitization on this DHCP client configuration endpoint enables attackers to inject shell commands through the web interface.
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 device modelAccess the device console or web interface and check the system information or model number to confirm it is a Ruijie RG-UAC 6000 series device (CC, E10, E10c, E20, E20c, E20m, E50, or E50c).Affected if Device is any Ruijie RG-UAC 6000 series model listed in the affected products.
-
Verify web interface accessibilityConfirm the device web management interface is reachable on the network by accessing the device IP via HTTP/HTTPS.Affected if The web interface is exposed and accessible from a network where attackers could reach it.
-
Check for vulnerable endpoint exposureAttempt to access or probe the path /view/dhcp/dhcpClient/dhcp_client_commit.php on the device web server to confirm the endpoint exists.Affected if The DHCP client configuration endpoint is present and reachable.
-
Review access logs for injection attemptsExamine the device web server logs or security logs for requests to the dhcp_client_commit.php endpoint containing suspicious patterns in the ifName parameter, such as shell metacharacters (;, |, &&, $( ), backticks).Affected if Log entries show command injection attempts or unusual ifName parameter values targeting this endpoint.
-
Check for unauthorized command executionReview system logs, shell history, or network device logs for any unexpected commands, new scheduled tasks, or outbound connections initiated from the device that were not authorized by administrators.Affected if Evidence exists of arbitrary command execution, new processes, or unauthorized changes to the device configuration.
A user is affected if they operate any Ruijie RG-UAC 6000 series model with its web management interface exposed to an untrusted network, as the vulnerability resides in the DHCP client configuration endpoint accessible via the web interface.
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 network access controls to restrict exposure of the management interface, deploy WAF rules to detect and block command injection patterns in the ifName parameter, and contact vendor for official patch; consider compensating controls or alternative solutions if vendor remains unresponsive.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4502 — 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-4502 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