dbcve.org
Command InjectionWeakness · CWE-77

CVE-2023-47356

HIGH · 8.8 CVSS v3.1 Published 2025-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Mingyu Security Gateway before v3.0-5.3p was discovered to contain a remote command execution (RCE) vulnerability via the log_type parameter at /log/fw_security.mds.

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

Mingyu Security Gateway contains an unauthenticated command injection vulnerability in the web interface. The log_type parameter at /log/fw_security.mds does not properly sanitize user input before passing it to system calls, allowing remote attackers to execute arbitrary OS commands by injecting shell metacharacters.

MitigationUpgrade to Mingyu Security Gateway v3.0-5.3p or later. As a temporary measure, restrict network access to the management interface and implement WAF rules to detect and block malicious patterns in the log_type parameter.

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
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 checks

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

  1. Identify if Mingyu Security Gateway is installed
    Check system inventory, running services, or installed software lists for 'Mingyu Security Gateway' or 'MSG' components. Review network services listening on management ports (typically 443, 8443, or custom web UI ports).
    Affected if The product is present and the web management interface is running.
  2. Determine the installed version
    Access the web interface admin panel and navigate to System > About, System > Status, or Help > Version. Alternatively, check for version files in the installation directory or examine the HTTP Server header if exposed.
    Affected if Version is below v3.0-5.3p (the patched release).
  3. Verify the vulnerable endpoint is accessible
    Attempt to access the path /log/fw_security.mds via HTTP or HTTPS on the management interface IP/hostname. A 200 OK response indicates the endpoint exists.
    Affected if The endpoint responds (is reachable and not blocked by network ACLs).
  4. Confirm web interface authentication is not enforced
    Send a crafted request to /log/fw_security.mds without providing session cookies or authentication tokens. Check if the application processes the request or returns an authentication error.
    Affected if The endpoint accepts requests without requiring valid authentication credentials.
  5. Check network exposure of management interface
    Review firewall rules, ACLs, or network segmentation to determine if the management interface (port 443/8443) is exposed to untrusted networks or the internet.
    Affected if The management web interface is reachable from untrusted networks (WAN/Internet).

You are affected if Mingyu Security Gateway is installed with a version below v3.0-5.3p, the /log/fw_security.mds endpoint is accessible, and the management interface is reachable from your network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Mingyu Security Gateway v3.0-5.3p or later. As a temporary measure, restrict network access to the management interface and implement WAF rules to detect and block malicious patterns in the log_type parameter.

Recommended fix Moderate confidence

v3.0-5.3p or later

  1. 1. Identify the current version of Mingyu Security Gateway by checking the system administration interface or running the appropriate version command
  2. 2. If the current version is earlier than v3.0-5.3p, plan for an upgrade to v3.0-5.3p or later
  3. 3. Before upgrading, perform a full backup of the current configuration
  4. 4. Obtain the v3.0-5.3p or later release from the official vendor (Mingyu)
  5. 5. Apply the upgrade following the vendor's documented upgrade procedure
  6. 6. After upgrade, verify the version has been successfully updated
  7. 7. Test the /log/fw_security.mds endpoint to confirm the vulnerability is remediated
  8. 8. Monitor for any unusual behavior following the upgrade
Caveat Review vendor release notes for v3.0-5.3p to check for any configuration or feature changes that may impact your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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