dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-51027

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Ruijie NBR800G gateway NBR_RGOS_11.1(6)B4P9 is vulnerable to command execution in /itbox_pi/networksafe.php via the province parameter.

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 confidence

The Ruijie NBR800G gateway running NBR_RGOS_11.1(6)B4P9 contains a command injection vulnerability in the /itbox_pi/networksafe.php script. The 'province' parameter is not properly sanitized, allowing authenticated attackers to inject and execute arbitrary operating system commands via the web interface.

MitigationApply available vendor firmware patches for CVE-2024-51027. If no patch is available, restrict network access to the management interface and consider deploying compensating controls such as WAF rules to filter malicious request patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router's web management interface or check CLI output for the model name (NBR800G) and firmware version string
    Affected if The device is a Ruijie NBR800G gateway running NBR_RGOS firmware
  2. Check the firmware version
    In the web interface, look under System Status or Maintenance > Firmware Upgrade to view the exact OS version; or run 'show version' via CLI
    Affected if The firmware version is NBR_RGOS_11.1(6)B4P9 or falls within the 11.1(6)Bxx branch (vulnerable to command injection in the 'province' parameter)
  3. Verify the vulnerable script is present
    Attempt to access the URI '/itbox_pi/networksafe.php' via HTTP/HTTPS to confirm the script exists on the device
    Affected if The script responds (even with an error), indicating the vulnerable endpoint is enabled
  4. Confirm web management interface is exposed
    Determine if the router's HTTP/HTTPS management ports (typically 80/443) are reachable from the network
    Affected if The web interface is accessible, allowing authenticated users to reach the vulnerable parameter

You are affected if you have a Ruijie NBR800G running NBR_RGOS_11.1(6)B4P9 (or similar 11.1(6)Bxx version) with the web management interface accessible and the /itbox_pi/networksafe.php script present, as an authenticated attacker could inject commands via the 'province' parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available vendor firmware patches for CVE-2024-51027. If no patch is available, restrict network access to the management interface and consider deploying compensating controls such as WAF rules to filter malicious request patterns.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-51027 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-51027 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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