CVE-2023-34365
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack-based buffer overflow exists in the nvram_restore function within libutils.so on Yifan YF325 routers (firmware v1.0_20221108). The function fails to properly bounds-check data received via network requests before copying into a fixed-size stack buffer, allowing remote attackers to overwrite return addresses and potentially achieve remote code execution with the privileges of the affected service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0_20221108CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface, or SSH prompt for 'Yifan YF325' or 'Yf325' brandingAffected if The device is a Yifan YF325 router
-
Check firmware versionAccess the router's web administration interface and look for firmware version information, typically under 'System' or 'Status' settings. Alternatively, check via CLI if telnet/SSH is enabledAffected if Firmware version equals 1.0_20221108 exactly
-
Confirm libutils.so is presentIf CLI access is available, check for the presence of /lib/libutils.so or similar paths where utility libraries are stored on the deviceAffected if The vulnerable library file exists on the device
-
Determine if network service using nvram_restore is exposedCheck router firewall rules or port forwarding configuration to see if the service handling nvram_restore requests (typically on custom ports) is accessible from the WAN or untrusted networksAffected if The nvram_restore network service is exposed to untrusted network interfaces
-
Look for signs of compromiseReview router logs for unexpected or malformed nvram_restore requests, unusual new processes, or modifications to startup scripts and configurationsAffected if Logs show anomalous nvram_restore traffic or unexpected system changes
A Yifan YF325 router running firmware version 1.0_20221108 with the nvram_restore service exposed to network is affected by this vulnerability
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to vendor-provided patched firmware if available; otherwise, restrict network access to the affected service and implement network segmentation to reduce exposure until a patch can be applied.
- Consultation6.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34365 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data