CVE-2025-4347
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 vulnerability was found in D-Link DIR-600L up to 2.07B01. It has been declared as critical. Affected by this vulnerability is the function formWlSiteSurvey. The manipulation of the argument host leads to buffer overflow. The attack can be launched remotely. This vulnerability only affects products that are no longer supported by the maintainer.
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 D-Link DIR-600L wireless router (firmware up to 2.07B01) in the formWlSiteSurvey function. The host argument is not properly bounds-checked, allowing an attacker to overflow a buffer via specially crafted HTTP requests to the router's web interface. The vulnerability is remotely exploitable and rated critical due to the potential for complete device compromise.
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<= 2.07b01CVSS 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.
-
Confirm device model is D-Link DIR-600LAccess the router's web interface and check the device information page, or look for the physical device label showing the model numberAffected if Device is not a D-Link DIR-600L, this CVE does not apply
-
Check firmware versionLog into the router's web interface and navigate to Status or System Info page to view the firmware version. The version is typically displayed as something like '2.07B01' or similarAffected if Firmware version is 2.07B01 or lower (any version up to and including 2.07b01)
-
Verify HTTP management interface is activeAttempt to access the router's web interface by entering the router's IP address in a web browser. The service typically runs on port 80Affected if HTTP service is running and accessible on the router
-
Check if formWlSiteSurvey function is reachableThe vulnerable function handles wireless site survey requests. Check if the wireless functionality is enabled and the web interface is accessible without authentication restrictionsAffected if Wireless features are enabled and the management web interface is exposed (even on local network)
You are affected if you have a D-Link DIR-600L router running firmware version 2.07B01 or lower with its web interface 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.
dbcve · scopedSince D-Link no longer supports the DIR-600L, the primary remediation is to replace the end-of-life device with a currently supported model. If immediate replacement is not feasible, network segmentation and firewall rules to restrict access to the router's management interface should be implemented as compensating controls.
- This vulnerability affects D-Link DIR-600L firmware versions up to and including 2.07b01.
- The affected product is explicitly stated as 'no longer supported by the maintainer' in the official description.
- No official firmware patch or security update is available for this vulnerability.
- Replace the end-of-life D-Link DIR-600L with a currently supported router from D-Link or another vendor.
- If replacement is not immediately possible, place the device behind a properly configured firewall with restricted inbound access to minimize exposure.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4347 — 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-2025-4347 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