Cyber Resilience

CVE-2025-14572

Memory Safety in Utt 512W Firmware ≤ 1.7.7-171114

Public PoCMemory Safety
Published
12 December 2025
Modified
12 January 2026
Patch / advisory
View advisory
CVSS Score v4 7.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.035 88th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2025-14572 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Utt 512W Firmware. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked in the top 12% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-14572 is a memory corruption vulnerability (CWE-119) in UTT 进取 512W devices running firmware versions up to 1.7.7-171114. The flaw affects an unknown part of the /goform/formWebAuthGlobalConfig file, where manipulation of the "hidcontact" argument triggers the corruption.

Remote exploitation is possible by an attacker with low privileges (PR:L) over the network (AV:N), requiring low complexity (AC:L) and no user interaction (UI:N). The CVSS v3.1 base score of 8.8 (C:H/I:H/A:H/S:U) indicates high impacts on confidentiality, integrity, and availability, potentially enabling arbitrary code execution or system compromise.

Advisories from VulDB and a GitHub issue (https://github.com/alc9700jmo/CVE/issues/21) confirm the exploit has been made public. The vendor was contacted early for disclosure but provided no response, and no patches or specific mitigations are detailed in the references.

EU & UK References

Vulnerability Data

A vulnerability was found in UTT 进取 512W up to 1.7.7-171114. This affects an unknown part of the file /goform/formWebAuthGlobalConfig. Performing manipulation of the argument hidcontact results in memory corruption. Remote exploitation of the attack is possible. The exploit has…

more

been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)
CWE-119

Related Threats

MITRE ATT&CK Enterprise Techniques

T1055 Process Injection Stealth
Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-15428Same product: Utt 512W
CVE-2025-14535Same product: Utt 512W
CVE-2025-15429Same product: Utt 512W
CVE-2025-15431Same product: Utt 512W
CVE-2025-15430Same product: Utt 512W
CVE-2025-14534Same product: Utt 512W
CVE-2025-15090Same product: Utt 512W
CVE-2025-15089Same product: Utt 512W
CVE-2025-15091Same product: Utt 512W
CVE-2025-14191Same product: Utt 512W

Affected Assets

utt
512w firmware
≤ 1.7.7-171114

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

SI-10 Information Input Validation partial match

Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.

SI-16 Memory Protection partial match

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.

References