CVE-2023-24479
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 · uneditedAn authentication bypass vulnerability exists in the httpd nvram.cgi functionality of Yifan YF325 v1.0_20221108. A specially crafted network request can lead to arbitrary command execution. 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 · moderate confidenceA critical authentication bypass vulnerability exists in the Yifan YF325 router's httpd nvram.cgi component (firmware v1.0_20221108). The flaw allows unauthenticated attackers to send specially crafted network requests that bypass authentication checks and achieve arbitrary command execution on the affected device.
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 router modelCheck the device label or web interface for the model number to confirm it is a Yifanwireless YF325 routerAffected if The device is a Yifan YF325 router
-
Check the firmware versionAccess the router web interface and look in the Administration, System, or Firmware upgrade section for the installed firmware version, or run 'nvram get firmware_version' via telnet/SSH if availableAffected if The firmware version is exactly 1.0_20221108
-
Verify httpd service is runningCheck if the httpd web server process is active on the device via 'ps' command or by accessing the router web login pageAffected if The httpd service is running and the web interface is accessible
-
Confirm nvram.cgi is accessibleAttempt to access the nvram.cgi endpoint via HTTP (e.g., http://<router-ip>/cgi-bin/nvram.cgi) - no authentication should be required for the vulnerability checkAffected if The nvram.cgi endpoint responds to requests without requiring authentication
-
Check network exposureDetermine if the router management interface is directly exposed to the internet or an untrusted network, or review firewall rules for port 80/443 forwarding to the routerAffected if The router HTTP/HTTPS management ports are accessible from untrusted networks
The environment is affected if the device is a Yifan YF325 router running firmware version 1.0_20221108 with the httpd service accessible on the network.
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 the latest vendor firmware update when available. As an interim measure, isolate the device behind a firewall or VLAN to restrict network access to trusted users only, since exploitation requires only network access.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24479 — 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-24479 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