Security readout for executives and security teams
Plain-English summary
CVE-2023-25094 affects Milesight UR32L firmware v32.3.0.5. A high-privileged attacker can send crafted HTTP requests that may trigger buffer overflows and allow arbitrary code execution. The issue is serious, but the provided sources do not show active exploitation or a named fixed version.
Executive priority
Treat this as a high-priority edge-device risk if affected UR32L routers are deployed. Prioritize inventory, management-plane isolation, and vendor update review before broader operational changes.
Technical view
The flaw is a CWE-121 stack-based buffer overflow in the vtysh_ubus binary. Talos attributes it to unsafe sprintf usage in into_class_node involving class_name or old_class_name. The CVSS v3.1 score is 7.2, with network access, low complexity, high privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is likely limited to organizations running Milesight UR32L devices on firmware v32.3.0.5 where the HTTP management path is reachable by high-privileged users or compromised administrative accounts.
Exploitation context
The source bundle says a specially crafted HTTP request can lead to arbitrary code execution by an attacker with high privileges. KEV status is false, and the supplied sources do not document active exploitation.
Researcher notes
Do not generalize beyond Milesight UR32L v32.3.0.5 from the supplied evidence. The sources identify vtysh_ubus, into_class_node, and class_name or old_class_name, but do not provide a fixed version or active exploitation evidence.
Mitigation direction
- Identify Milesight UR32L devices and confirm firmware versions.
- Check Milesight guidance for fixed firmware or official mitigation steps.
- Restrict HTTP management access to trusted administrative networks only.
- Review and limit high-privileged accounts on affected devices.
- Monitor for unexpected configuration changes or administrative activity.
Validation and detection
- Inventory UR32L devices and record firmware version v32.3.0.5 matches.
- Confirm whether HTTP management interfaces are internet-exposed or broadly reachable.
- Review access controls for high-privileged device accounts.
- Check vendor advisories for fixed firmware before remediation planning.
- Document compensating controls where upgrades are 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-25094 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.