Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2023-34365: CWE-121: Stack-based Buffer Overflow in Yifan YF325

0
Critical
VulnerabilityCVE-2023-34365cvecve-2023-34365cwe-121
Published: Wed Oct 11 2023 (10/11/2023, 15:14:30 UTC)
Source: CVE Database V5
Vendor/Project: Yifan
Product: YF325

Description

A stack-based buffer overflow vulnerability exists in the libutils.so nvram_restore functionality of Yifan YF325 v1.0_20221108. A specially crafted network request can lead to a buffer overflow. An attacker can send a network request to trigger this vulnerability.

AI-Powered Analysis

AILast updated: 11/04/2025, 20:30:45 UTC

Technical Analysis

CVE-2023-34365 is a stack-based buffer overflow vulnerability identified in the libutils.so library, specifically within the nvram_restore functionality of the Yifan YF325 device version v1.0_20221108. The vulnerability stems from improper bounds checking when processing network requests, allowing an attacker to send a specially crafted packet that overflows a stack buffer. This overflow can corrupt the stack, potentially enabling arbitrary code execution, denial of service, or complete system compromise. The vulnerability is remotely exploitable over the network without requiring any privileges or user interaction, making it highly accessible to attackers. The CVSS v3.1 base score of 9.8 reflects the critical nature of this flaw, with attack vector being network (AV:N), no attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and full impact on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no public exploits have been reported yet, the vulnerability’s characteristics suggest it could be weaponized rapidly. The affected product, Yifan YF325, is an embedded device likely used in IoT or specialized industrial applications. The lack of available patches at the time of reporting increases the urgency for organizations to implement alternative mitigations. The vulnerability is classified under CWE-121, indicating a classic stack-based buffer overflow issue, a well-known and dangerous software flaw.

Potential Impact

For European organizations, exploitation of this vulnerability could lead to severe consequences including unauthorized access, data theft, device manipulation, or complete denial of service. Given the device’s embedded nature, it may be part of critical infrastructure, industrial control systems, or IoT deployments, where compromise could disrupt operations or safety systems. The ability to exploit remotely without authentication increases the attack surface significantly. Organizations relying on Yifan YF325 devices in sectors such as manufacturing, utilities, transportation, or telecommunications could face operational disruptions and data breaches. The impact extends beyond individual devices, as compromised devices could be leveraged as footholds for lateral movement or as part of botnets. The absence of known exploits currently provides a window for proactive defense, but the critical severity demands immediate attention to prevent potential exploitation. The reputational and regulatory consequences for European entities could be substantial, especially under GDPR and other data protection frameworks if personal or sensitive data is exposed.

Mitigation Recommendations

Since no patches are currently available, European organizations should implement the following specific mitigations: 1) Isolate Yifan YF325 devices on segmented network zones with strict access controls to limit exposure to untrusted networks. 2) Deploy network intrusion detection and prevention systems (IDS/IPS) configured to detect anomalous or malformed packets targeting the nvram_restore functionality or unusual traffic patterns to these devices. 3) Apply strict firewall rules to restrict inbound traffic to only trusted sources and necessary protocols. 4) Monitor device logs and network traffic for signs of exploitation attempts or unusual behavior. 5) Engage with the vendor to obtain updates or patches and plan for timely deployment once available. 6) Conduct an inventory and risk assessment to identify all affected devices and prioritize their protection or replacement. 7) Consider implementing network-level rate limiting and anomaly detection to reduce the risk of exploitation. 8) Educate operational technology (OT) and IT teams about the vulnerability and response procedures. These targeted measures go beyond generic advice by focusing on network segmentation, monitoring, and vendor engagement specific to the Yifan YF325 environment.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
talos
Date Reserved
2023-06-12T16:02:35.314Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690a53242a90255b94da666c

Added to database: 11/4/2025, 7:25:24 PM

Last enriched: 11/4/2025, 8:30:45 PM

Last updated: 11/6/2025, 7:41:36 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats