A vulnerability was identified in UTT HiPER 1250GW up to v3.2.7-210907-180535. The impacted element is the function strcpy of the file /goform/getOneApConfTempEntry. The manipulation of the argument tempName leads to stack-based buffer overflow. The attack can be initiated remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
Security readout for executives and security teams
Plain-English summary
A remotely reachable flaw in the UTT HiPER 1250GW can overflow device memory when processing a crafted tempName value. Successful exploitation could disrupt the gateway or compromise its confidentiality and integrity. Public proof-of-concept material increases risk, but the supplied sources do not establish active exploitation or identify a vendor fix.
Executive priority
Treat confirmed affected, reachable devices as an urgent remediation item because compromise could affect gateway confidentiality, integrity, and availability. Prioritize internet-facing systems first. Where no vendor-supported fix can be verified, reduce reachability immediately and evaluate isolation or replacement while monitoring for suspicious activity.
Technical view
The /goform/getOneApConfTempEntry handler reportedly passes attacker-controlled tempName data to strcpy, causing a stack-based buffer overflow. The CVSS v2 vector indicates network access, low complexity, single authentication, and complete confidentiality, integrity, and availability impact. Reported affected firmware is up to v3.2.7-210907-180535.
Likely exposure
Exposure is limited to UTT HiPER 1250GW deployments running the reported affected firmware where the vulnerable management handler is reachable. Internet-accessible or broadly reachable administration interfaces present greater concern. The supplied evidence does not establish how commonly the product is deployed or whether default configurations expose the endpoint.
Exploitation context
Public proof-of-concept material is referenced, making independent reproduction more plausible. However, this CVE is not identified as CISA KEV, and the supplied sources provide no evidence of active exploitation. The report says the vendor did not respond, leaving patch availability and official remediation unconfirmed.
Researcher notes
The root cause is reported as unbounded copying into stack memory through strcpy. Evidence supports remote initiation and public proof-of-concept availability, but not exploitation in the wild. Vendor confirmation, patched-version information, endpoint authentication behavior, and reliable indicators of compromise are absent from the supplied bundle.
Mitigation direction
Inventory UTT HiPER 1250GW devices and record their exact firmware versions.
Restrict management interfaces to trusted administrative networks and authenticated operators.
Block unnecessary access to the affected handler at network or reverse-proxy controls.
Check UTT guidance for fixed firmware or supported mitigations before applying changes.
Isolate or replace exposed devices if no verified fixed firmware is available.
Monitor gateways for crashes, restarts, configuration changes, and unusual management requests.
Validation and detection
Confirm each device model and firmware version through trusted inventory or administrative records.
Determine whether the management interface is reachable from the internet or untrusted networks.
Verify authentication requirements and access-control rules protecting the affected handler.
Review device and perimeter logs for unusual requests, crashes, or unexplained restarts.
Confirm any proposed firmware version or mitigation against current vendor guidance.
Use safe, authorized testing without sending overflow payloads to production devices.
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 · low confidence lookup
CWE-119: 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.
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.
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.
4CVSS vectors
6Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
4 official scores
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.