CVE-2023-35056
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 buffer overflow vulnerability exists in the httpd next_page functionality of Yifan YF325 v1.0_20221108. A specially crafted network request can lead to command execution. An attacker can send a network request to trigger this vulnerability.This buffer overflow is in the next_page parameter in the cgi_handler 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 · high confidenceA buffer overflow vulnerability exists in the httpd web server component of Yifan YF325 v1.0_20221108 firmware. The overflow occurs in the next_page parameter within the cgi_handler function, allowing an attacker to overwrite memory and achieve remote command execution via specially crafted HTTP requests.
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, admin web interface, or SSH banner for the exact model number. Look for Yifan YF325, Yifanwireless Yf325, or similar branding.Affected if The device is NOT a Yifan YF325 model - if it is a different model, this CVE does not apply.
-
Determine the firmware versionAccess the device's admin web interface (usually at http://192.168.1.1) and navigate to the Status or System section to view the firmware version. Alternatively, check via SSH/Telnet if enabled using commands like 'cat /proc/version' or 'fw_printenv' if available.Affected if The firmware version is exactly 1.0_20221108 - only this specific version is listed as affected.
-
Verify the httpd web server is runningIf you have shell access (SSH/Telnet), run 'ps | grep httpd' or check for the httpd process listening on port 80/443.Affected if The httpd process is running and exposed on the network - the vulnerability exists in this component.
-
Confirm network exposure of the HTTP serviceCheck if the device's HTTP service (port 80 or 443) is accessible from untrusted networks. Use 'netstat -tlnp' or similar to verify listening interfaces, or scan the device from an external IP using nmap to confirm port accessibility.Affected if The HTTP service is exposed to untrusted networks without firewall protection - this is required for an attacker to send the malicious HTTP requests.
You are affected only if you have a Yifan YF325 device running firmware version 1.0_20221108 with the httpd web server exposed to network attackers.
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-supplied firmware update when available; until then, restrict network access to the device's HTTP service using firewall rules or network segmentation to prevent unauthenticated attackers from sending malicious requests.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35056 — 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-35056 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