CVE-2005-1680
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 · uneditedD-Link DSL-502T, DSL-504T, DSL-562T, and DSL-G604T, when /cgi-bin/firmwarecfg is executed, allows remote attackers to bypass authentication (1) if their IP address already exists in /var/tmp/fw_ip or (2) if their request is the first, which causes /var/tmp/fw_ip to be created and contain their IP address.
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 confidenceThe D-Link routers DSL-502T, DSL-504T, DSL-562T, and DSL-G604T contain an authentication bypass vulnerability in the /cgi-bin/firmwarecfg CGI script. The authentication mechanism relies on a file (/var/tmp/fw_ip) containing allowed IP addresses. An attacker can bypass authentication by either having their IP already present in this file or by being the first request to the endpoint, which creates the file with their IP address.
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 dataall versionsall versionsall versionsall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 log into the web management interface to confirm the exact model number. Affected models are DSL-502T, DSL-504T, DSL-562T, and DSL-G604T.Affected if The device is any of these four D-Link models.
-
Confirm web interface accessibilityAttempt to access the router web management interface (typically http://192.168.0.1 or http://192.168.1.1) from a browser. Note whether the interface responds.Affected if The web management interface is reachable on the network.
-
Test the firmwarecfg endpointSend an HTTP request to http://[router_ip]/cgi-bin/firmwarecfg without providing any authentication credentials. Observe whether the endpoint returns a response instead of redirecting to a login page.Affected if The /cgi-bin/firmwarecfg endpoint responds without requiring authentication.
-
Inspect the fw_ip fileIf you have telnet or SSH access to the router, check the contents of /var/tmp/fw_ip using the command: cat /var/tmp/fw_ipAffected if The file contains your current IP address or any unexpected IP addresses.
A user is affected if they operate any of the four D-Link models listed and their router web interface is accessible, since the authentication bypass allows unauthenticated access to the firmwarecfg CGI script.
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 dataReplace affected devices as they are end-of-life and no longer receive security updates from D-Link. If continued operation is required, restrict access to the web management interface using firewall rules to trusted IP addresses only.
- Consultation2.0 h
- Implementation1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1680 — 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-2005-1680 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