Security readout for executives and security teams
Plain-English summary
CVE-2023-25090 affects Milesight UR32L routers running v32.3.0.5. A highly privileged attacker can trigger buffer overflows through HTTP handling and potentially run arbitrary code. This is serious for exposed or shared-admin devices, but the supplied sources do not show active exploitation.
Executive priority
Treat this as a high-priority router remediation item where UR32L devices are in sensitive networks or remotely managed. The privilege requirement lowers immediate internet-wide risk, but successful exploitation could compromise the device and disrupt operations.
Technical view
The issue is a CWE-121 stack buffer overflow in the vtysh_ubus binary. Talos attributes it to unsafe sprintf usage in handle_interface_acl involving interface and in_acl variables. CVSS 3.1 is 7.2 with network attack vector, low complexity, high privileges required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to Milesight UR32L devices on firmware v32.3.0.5. Risk is highest where the device management interface is reachable by administrators over networks with weak segmentation or where high-privilege credentials are broadly shared.
Exploitation context
The source bundle says exploitation requires high privileges and a specially crafted HTTP request. It does not identify public exploit activity, and the CVE is not marked as CISA KEV in the provided data.
Researcher notes
Evidence is strongest for affected version, vulnerable binary, vulnerable function, weakness class, and privilege requirement. The provided bundle does not include a fixed version, proof of active exploitation, or detailed vendor remediation status, so avoid assuming patch availability beyond checking official guidance.
Mitigation direction
- Check Milesight and Talos guidance for fixed firmware or official mitigations.
- Restrict HTTP management access to trusted admin networks only.
- Review and reduce high-privilege accounts on affected devices.
- Monitor administrative HTTP activity for unexpected configuration changes.
- Plan firmware remediation for any UR32L running v32.3.0.5.
Validation and detection
- Inventory Milesight UR32L devices and record firmware versions.
- Confirm whether v32.3.0.5 is present in production or remote sites.
- Review network paths to the device management interface.
- Verify high-privilege account ownership and recent administrative activity.
- Track vendor advisories for confirmed fixed versions.
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-25090 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.