LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47356: Mingyu Security Gateway before v3.0-5.3p was discovered to contain a remote command execution (RCE) vulnera...

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Mingyu Security Gateway versions before v3.0-5.3p have a high-severity remote command execution flaw. A user with some privileges could potentially make the gateway run unintended system commands, risking full compromise of confidentiality, integrity, and availability.

Executive priority

Treat this as a high-priority perimeter appliance issue. If the product is present, confirm version and management exposure quickly because compromise could affect the security gateway itself and downstream network trust.

Technical view

CVE-2023-47356 is a CWE-77 command injection issue in the log_type parameter of /log/fw_security.mds. The CVSS 3.1 vector is network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, and high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to organizations running Mingyu Security Gateway before v3.0-5.3p, especially where the management interface is reachable by users or networks beyond a tightly controlled admin segment.

Exploitation context

The bundle cites public researcher references, but does not establish active exploitation. The CVE is not marked KEV. The CVSS vector indicates exploitation requires network reachability and low privileges, with no user interaction.

Researcher notes

The source data lacks structured vendor, product, CPE, and formal patch advisory details. Analysis should stay tied to the CVE description, CVSS vector, and cited public references until authoritative vendor guidance is available.

Mitigation direction

  • Identify all Mingyu Security Gateway deployments and their versions.
  • Upgrade systems running versions before v3.0-5.3p according to vendor guidance.
  • Restrict management access to trusted administrative networks only.
  • Review accounts with access to gateway log or security functions.
  • Monitor vendor and CVE sources for clarified affected product metadata.

Validation and detection

  • Confirm whether any deployed gateway version is before v3.0-5.3p.
  • Check whether /log/fw_security.mds is reachable from untrusted networks.
  • Review logs for suspicious requests involving the log_type parameter.
  • Validate that low-privileged gateway users cannot access risky administrative functions.
  • Retest exposure after upgrade or access-control changes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47356 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-47356Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.