Security readout for executives and security teams
Plain-English summary
Milesight UR32L routers running firmware v32.3.0.5 contain buffer overflow flaws in a management component. A highly privileged attacker can send crafted HTTP requests that may execute code on the device. Business urgency is highest where these devices manage network connectivity or are reachable beyond tightly controlled admin networks.
Executive priority
Treat as high priority for any affected router that supports sensitive connectivity or has exposed administration. The high-privilege requirement lowers broad opportunistic risk, but successful exploitation could give full device compromise and disrupt network operations.
Technical view
CVE-2023-25087 is a CWE-121 stack buffer overflow in the Milesight UR32L vtysh_ubus binary. The issue is linked to unsafe sprintf use in firewall_handler_set, specifically index and to_dport handling. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, with high confidentiality, integrity, and availability impact.
Likely exposure
Confirmed scope is Milesight UR32L firmware v32.3.0.5. Exposure is most likely when the device HTTP management path is reachable and attackers can obtain or already hold high-privileged access. The source bundle provides no CPE list or broader version range.
Exploitation context
The sources describe specially crafted HTTP requests leading to arbitrary code execution, but require high privileges. The CVE is not marked CISA KEV in the provided bundle, and no cited source here confirms active exploitation in the wild.
Researcher notes
Analysis is limited to the provided CVE and Talos references. Key confirmed details are affected product/version, vulnerable binary, function, variables, CWE-121, CVSS vector, and high-privilege HTTP trigger. Patch status and broader firmware impact are not established in the supplied bundle.
Mitigation direction
- Inventory Milesight UR32L devices and identify firmware v32.3.0.5.
- Restrict HTTP management access to trusted admin networks or VPN.
- Review and harden high-privilege accounts on affected devices.
- Check Milesight or Talos guidance for fixed firmware or vendor workarounds.
- Prioritize upgrade or compensating controls once vendor guidance is confirmed.
Validation and detection
- Confirm device model and firmware version from asset records or administration interface.
- Verify management HTTP interfaces are not internet-exposed.
- Review recent high-privilege firewall configuration activity on affected devices.
- Check vulnerability management data for Milesight UR32L v32.3.0.5 findings.
- Document whether vendor remediation guidance is available for each affected asset.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupExecution 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 lookupCVE-2023-25087 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.