CVE-2023-35965
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 · uneditedTwo heap-based buffer overflow vulnerabilities exist in the httpd manage_post functionality of Yifan YF325 v1.0_20221108. A specially crafted network request can lead to a heap buffer overflow. An attacker can send a network request to trigger these vulnerabilities.This integer overflow result is used as argument for the malloc function.
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 · moderate confidenceTwo heap-based buffer overflow vulnerabilities exist in the httpd manage_post functionality of Yifan YF325 v1.0_20221108. An integer overflow allows a specially crafted network request to allocate an undersized heap buffer, which is then overflowed when the request data is written. This can lead to remote code execution.
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 device modelCheck the device label or web interface for model number YF325 or Yifanwireless Yf325Affected if Device is not a YF325 model
-
Check firmware versionAccess the device's admin web interface, typically at http://[device IP], and look for firmware version in system settings or status page. Alternatively, check the firmware file if you have access to it.Affected if Firmware version is not 1.0_20221108
-
Verify httpd service is runningAccess the device via SSH or telnet if available and run: ps | grep httpd or check if port 80/443 is listeningAffected if httpd service is not running or not accessible
-
Confirm httpd network exposureCheck if httpd is listening on all interfaces (0.0.0.0) rather than localhost only. Use: netstat -an | grep ':80\|:443' or nmap scan of the device from an external networkAffected if httpd is listening on external interfaces (not localhost/127.0.0.1 only)
-
Check if manage_post endpoint respondsSend a POST request to //cgi-bin/manage_post or similar endpoint accessible via the web interface. This may require authentication.Affected if The manage_post functionality is accessible via the web interface
A user is affected if they are running YF325 firmware version 1.0_20221108 with httpd exposed to network access, enabling remote exploitation via the manage_post buffer overflow.
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 dataApply vendor firmware update when available. Until then, disable remote httpd management access, network segment the device, and monitor for exploitation attempts.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35965 — 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-35965 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