dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2023-7304

CRITICAL · 9.3 CVSS v4.0 Published 2025-10-15
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
Ruijie RG-UAC Application Management Gateway contains a command injection vulnerability via the 'nmc_sync.php' interface. An unauthenticated attacker able to reach the affected endpoint can inject shell commands via crafted request data, causing the application to execute arbitrary commands on the host. Successful exploitation can yield full control of the application process and may lead to system-level access depending on the service privileges. VulnCheck has observed this vulnerability being targeted by the RondoDox botnet campaign.

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

Ruijie RG-UAC Application Management Gateway contains an unauthenticated command injection vulnerability in the nmc_sync.php interface. Attackers can inject arbitrary shell commands through crafted request data to the affected endpoint, achieving remote code execution with the privileges of the application process.

MitigationRestrict network access to the nmc_sync.php endpoint immediately using firewall rules or network segmentation; apply vendor-provided patches when available and validate input sanitization in the application layer.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Ruijie RG-UAC gateway installation
    Check system information or network services for Ruijie RG-UAC Application Management Gateway. Look for the product name in service banners, web interface titles, or system documentation. The service typically runs on common web ports (80/443).
    Affected if The target system is a Ruijie RG-UAC Application Management Gateway device or virtual appliance.
  2. Locate nmc_sync.php endpoint
    Attempt to access the path /nmc_sync.php on the web server. This is typically found in the web administration interface of the RG-UAC. Use curl or a browser to request: http://[target]/nmc_sync.php or https://[target]/nmc_sync.php
    Affected if The nmc_sync.php file exists and is accessible on the device.
  3. Verify interface is network accessible
    Check if the web interface and nmc_sync.php are exposed to untrusted networks. Review firewall rules, ACLs, or network segmentation configurations that control access to the RG-UAC management ports from external or untrusted internal IP addresses.
    Affected if The nmc_sync.php interface is reachable from untrusted networks without authentication requirements.
  4. Check for indicators of compromise
    Review web server access logs and application logs for unusual requests to nmc_sync.php, especially those containing shell metacharacters (such as ;, |, &&, $(...), backticks) or common command injection patterns. Also check for unexpected processes, new user accounts, or modified system files that may indicate prior exploitation.
    Affected if Log analysis reveals suspicious requests to nmc_sync.php containing command injection patterns, or system shows signs of unauthorized access.
  5. Compare installed version to patch status
    If possible, determine the installed RG-UAC firmware or software version through the administrative interface, CLI, or system files. Compare against any vendor release notes or security advisories for CVE-2023-7304 to identify if a patch has been applied.
    Affected if The installed version is older than the patched release or the patch status cannot be verified.

A system is affected if it is a Ruijie RG-UAC device with the nmc_sync.php interface exposed to untrusted networks and the vendor patch for CVE-2023-7304 has not been applied.

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 network access to the nmc_sync.php endpoint immediately using firewall rules or network segmentation; apply vendor-provided patches when available and validate input sanitization in the application layer.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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