CVE-2024-4506
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 20240428 and classified as critical. This vulnerability affects unknown code of the file /view/IPV6/ipv6Addr/ip_addr_edit_commit.php. The manipulation of the argument text_ip_addr/orgprelen/orgname leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-263110 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's IPv6 address management module (ip_addr_edit_commit.php). The text_ip_addr, orgprelen, and orgname parameters are not properly sanitized before being passed to system shell commands, allowing remote attackers to execute arbitrary OS commands on the affected device.
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 web interface or check the system information page to confirm the exact RG-UAC model number (6000 CC, E10, E10c, E20, E20c, E20m, E50, or E50c)Affected if The device is any Ruijie RG-UAC 6000 series model (all versions are affected)
-
Check firmware versionNavigate to the device admin panel, typically under System > Device Info or About, to view the installed firmware versionAffected if Any version is installed since all versions are affected according to the advisory
-
Verify IPv6 address management module accessibilityAttempt to access the path /ip_addr_edit_commit.php on the device management interface using a web browser or curl commandAffected if The script ip_addr_edit_commit.php is reachable and responds to requests
-
Inspect web server access logsReview the RG-UAC web server access logs (typically stored in /var/log/httpd/ or similar directory on the device) for any GET or POST requests to ip_addr_edit_commit.php containing suspicious characters like semicolons, pipes, or command separators in parameters text_ip_addr, orgprelen, or orgnameAffected if Log entries show requests to ip_addr_edit_commit.php with unusual parameter patterns indicating exploitation attempts
-
Monitor for unexpected system behaviorCheck for new or unexpected user accounts, scheduled tasks, or network connections originating from the RG-UAC device that were not configured by administratorsAffected if Unexpected accounts, cron jobs, or outbound connections are found on the device
A user is affected if they are running any Ruijie RG-UAC 6000 series firmware version with the management interface exposed to network access.
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 (ideally to admin-only networks), deploy WAF rules to detect command injection patterns in URL parameters, and monitor for indicators of compromise since the vendor has not released a patch.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4506 — 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-4506 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