Cyber Resilience

CVE-2023-34346

Memory Safety in Yifanwireless Yf325 Firmware 1.0_20221108

Published
11 October 2023
Modified
04 November 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.013 67th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2023-34346 is a critical-severity Active Debug Code (CWE-489) vulnerability in Yifanwireless Yf325 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A stack-based buffer overflow vulnerability exists in the httpd gwcfg.cgi get functionality of Yifan YF325 v1.0_20221108. A specially crafted network packet can lead to command execution. An attacker can send a network request to trigger this vulnerability.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-32645Same product: Yifanwireless Yf325
CVE-2023-31272Same product: Yifanwireless Yf325
CVE-2023-35965Same product: Yifanwireless Yf325
CVE-2023-35966Same product: Yifanwireless Yf325
CVE-2023-35967Same product: Yifanwireless Yf325
CVE-2023-35968Same product: Yifanwireless Yf325
CVE-2023-34365Same product: Yifanwireless Yf325
CVE-2023-34426Same product: Yifanwireless Yf325
CVE-2024-30307Shared CWE-787
CVE-2023-6228Shared CWE-787

Affected Assets

yifanwireless
yf325 firmware
1.0_20221108

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-489

Minimal functionality precludes inclusion of active debug code or diagnostic interfaces.

addresses: CWE-787

Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.

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 directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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.

detects

Security testing in development and acceptance catches active debug code before deployment.

prevents

Configuration management can disable or remove debug features through hardened baselines.

prevents

Secure development life cycle mandates removal of debug code before release.

prevents

Application security requirements can specify bounds-checking and safe memory handling.

prevents

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

References