LiveActive security incident?Get immediate response
CVE Record

CVE-2023-22365: An OS command injection vulnerability exists in the ys_thirdparty check_system_user functionality of Milesi...

An OS command injection vulnerability exists in the ys_thirdparty check_system_user functionality of Milesight UR32L v32.3.0.5. A specially crafted set of network packets can lead to command execution. An attacker can send a network request to trigger this vulnerability.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-22365 affects Milesight UR32L routers running v32.3.0.5. A privileged attacker who can reach the device over the network may trigger operating system command execution. Business risk is highest where these routers support remote sites, industrial connectivity, or exposed management paths.

Executive priority

Treat as a high-priority exposure review for any Milesight UR32L estate. Urgency increases if devices are internet reachable, manage operational connectivity, or use shared privileged credentials.

Technical view

The flaw is CWE-78 OS command injection in the ys_thirdparty check_system_user functionality of Milesight UR32L v32.3.0.5. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Milesight UR32L devices on firmware v32.3.0.5, especially where administrative access is reachable over untrusted networks. The provided sources do not identify other affected Milesight products or versions.

Exploitation context

The CVE states an attacker can send a network request with specially crafted packets to trigger command execution. CISA KEV status is false in the bundle, and no cited source here supports active exploitation.

Researcher notes

The source bundle identifies the affected function and impact but does not provide patch status, safe detection artifacts, or confirmed exploitation. Avoid expanding scope beyond Milesight UR32L v32.3.0.5 without additional vendor evidence.

Mitigation direction

  • Inventory Milesight UR32L devices and record firmware versions.
  • Check Milesight and Talos guidance for fixed firmware or official mitigations.
  • Restrict management access to trusted administrative networks only.
  • Remove any unnecessary external exposure of device management services.
  • Review privileged accounts and rotate credentials if compromise is suspected.

Validation and detection

  • Confirm whether any UR32L device runs firmware v32.3.0.5.
  • Verify management interfaces are not reachable from untrusted networks.
  • Check whether vendor-recommended firmware or mitigations are applied.
  • Review device and network logs for abnormal administrative activity.
  • Document compensating controls for devices awaiting vendor guidance.
Prepared
Confidence
high
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-78: 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-22365 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
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
MilesightUR32Lv32.3.0.5Listed
Weakness

CWE details

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

CWE-78 · source CWE mapping

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

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