CVE-2024-2909
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 was found in Ruijie RG-EG350 up to 20240318. Affected by this vulnerability is the function setAction of the file /itbox_pi/networksafe.php?a=set of the component HTTP POST Request Handler. The manipulation of the argument bandwidth 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-257977 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-EG350 routers where the setAction function in /itbox_pi/networksafe.php accepts user-supplied bandwidth parameter without sanitization, allowing remote attackers to inject arbitrary OS commands via crafted HTTP POST requests.
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 data<= 2024-03-18CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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-EG350Log into the router admin interface or check the device label/marketing specifications to verify the exact model number.Affected if The device is NOT a Ruijie RG-EG350 router (other models are not affected by this specific CVE).
-
Check installed firmware versionAccess the router web interface, typically at the management IP, and navigate to System Status or Firmware Upgrade section to find the current firmware version and build date.Affected if The firmware version is dated 2024-03-18 or earlier, or the version number is unknown but the build date is on or before that date.
-
Verify the vulnerable PHP script existsAttempt to access the file /itbox_pi/networksafe.php on the router's web server. This may require authentication or may be accessible without authentication depending on configuration.Affected if The file /itbox_pi/networksafe.php exists and is accessible via HTTP/HTTPS to the requester.
-
Determine if the management interface is network-accessibleCheck network ACLs, firewall rules, or NAT configurations to determine if the router's web management interface (port 80/443) is reachable from network segments outside the trusted administrative network.Affected if The router management interface (HTTP/HTTPS) is accessible from untrusted networks, particularly the internet.
You are affected if you have a Ruijie RG-EG350 router running firmware dated 2024-03-18 or earlier, and the /itbox_pi/networksafe.php endpoint is accessible to attackers on your network.
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 limit exposure of the management interface, deploy WAF rules to detect command injection patterns, and contact vendor for firmware updates; consider network segmentation or device replacement if no patch becomes available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2909 — 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-2909 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