Security readout for executives and security teams
Plain-English summary
CVE-2023-25099 is a high-severity flaw in Milesight UR32L v32.3.0.5. A highly privileged attacker could send a malicious HTTP request that triggers a buffer overflow and may execute code on the device. This is mainly urgent where affected devices are remotely managed or reachable by many administrators.
Executive priority
Treat this as a high-priority infrastructure hygiene issue for environments using affected Milesight UR32L devices. It is not cited as actively exploited, but successful abuse could give a privileged attacker code execution on network equipment.
Technical view
The issue is a stack-based buffer overflow in the Milesight UR32L v32.3.0.5 vtysh_ubus binary. Talos attributes it to an unsafe sprintf pattern in set_qos, involving the dest variable. The CVSS 3.1 vector is 7.2, network reachable, low complexity, high privileges required, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to Milesight UR32L devices running v32.3.0.5, based on the provided sources. Risk is higher when the HTTP management surface is reachable by privileged users over broad networks or remote administration paths.
Exploitation context
The source bundle does not indicate CISA KEV listing or active exploitation. The described attack requires high privileges and a specially crafted HTTP request. Public evidence supports potential arbitrary code execution, but not unauthenticated exploitation.
Researcher notes
The provided evidence names one affected version and one vulnerable code path: vtysh_ubus set_qos with dest. The sources do not provide a confirmed patch version in the bundle, so remediation guidance should be verified against current vendor materials.
Mitigation direction
- Inventory Milesight UR32L devices and identify any running v32.3.0.5.
- Check Milesight and Talos guidance for fixed firmware or vendor remediation details.
- Restrict HTTP management access to trusted administrative networks only.
- Review and reduce privileged accounts allowed to manage affected devices.
- Monitor affected devices for unusual administrative activity or unexpected instability.
Validation and detection
- Confirm device model and firmware version through approved administrative inventory methods.
- Verify whether the HTTP management interface is exposed beyond trusted administration networks.
- Review privileged account lists and recent administrative access logs.
- Check vendor advisories for a fixed version before planning remediation.
- Document compensating controls where immediate firmware remediation is unavailable.
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-25099 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.