dbcve.org
Rg Nbr2100g E FirmwareOperating system · Ruijienetworks

CVE-2022-27982

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
RG-NBR-E Enterprise Gateway RG-NBR2100G-E was discovered to contain a remote code execution (RCE) vulnerability via the fileName parameter at /guest_auth/cfg/upLoadCfg.php.

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 · moderate confidence

A remote code execution vulnerability exists in the RG-NBR2100G-E gateway's file upload functionality at /guest_auth/cfg/upLoadCfg.php. The fileName parameter accepts arbitrary file names without proper validation, allowing attackers to upload and execute malicious PHP scripts on the affected system.

MitigationRestrict access to the /guest_auth/cfg/upLoadCfg.php endpoint and implement strict file type validation with content inspection before allowing any uploads. Apply vendor patches when available.

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
Rg Nbr2100g E FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm device model is RG-NBR2100G-E
    Access the device administration interface or check the device label/menu for the exact model number. Use commands such as 'show version' via CLI or inspect the web interface header for the model designation.
    Affected if The device model is Ruijienetworks RG-NBR2100G-E (any firmware version).
  2. Identify the firmware version
    In the device admin panel, navigate to System Status or Diagnostics. Alternatively, use the CLI command 'show version' or check the 'About' section in the web management interface.
    Affected if Any firmware version is installed since all versions are affected.
  3. Verify /guest_auth/cfg/upLoadCfg.php is accessible
    From a network-connected host, attempt to access the URL 'http://<device-ip>/guest_auth/cfg/upLoadCfg.php' using a web browser or curl command. A successful HTTP response (even an error page) indicates the endpoint exists.
    Affected if The endpoint returns any HTTP response, indicating it is exposed.
  4. Test file upload functionality
    Send a POST request to /guest_auth/cfg/upLoadCfg.php with a file upload payload containing a test file. Use a tool like curl: 'curl -X POST -F "fileName=test.php" -F "[email protected]" http://<device-ip>/guest_auth/cfg/upLoadCfg.php'.
    Affected if The upload request is accepted without rejection or validation errors, confirming the vulnerability is exploitable.
  5. Check for existing unexpected uploaded files
    If web server directory listing is enabled, navigate to common upload directories such as /guest_auth/cfg/ or /uploads/ using a browser. Otherwise, use file system access via admin panel or FTP to enumerate any .php files that were not intentionally deployed.
    Affected if Unexpected .php files are found in the upload directory.

If the device is an RG-NBR2100G-E and the /guest_auth/cfg/upLoadCfg.php endpoint is accessible and accepts file uploads, the environment is affected by CVE-2022-27982.

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

Restrict access to the /guest_auth/cfg/upLoadCfg.php endpoint and implement strict file type validation with content inspection before allowing any uploads. Apply vendor patches when available.

Fix this in Rg Nbr2100g E Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27982 — 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-2022-27982 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