dbcve.org
Di 604Hardware / appliance · D Link

CVE-2004-0661

MEDIUM · 5.0 CVSS v2.0 Published 2004-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Integer signedness error in D-Link AirPlus DI-614+ running firmware 2.30 and earlier allows remote attackers to cause a denial of service (IP lease depletion) via a DHCP request with the LEASETIME option set to -1, which makes the DHCP lease valid for thirteen or more years.

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 confidence

Integer signedness error in D-Link AirPlus DI-614+ DHCP server allows remote attackers to send DHCP requests with LEASETIME set to -1, which is not properly validated as a negative value, causing the lease to be valid for 13+ years and depleting the IP address pool.

MitigationUpdate router firmware to a version newer than 2.30 if available; if no firmware update exists, replace the end-of-life device with a supported router.

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
Di 604Hardware / appliance
Affected:all versions
Di 614\+Hardware / appliance
Affected:= 2.30
Di 624Hardware / appliance
Affected:= 1.28

CVSS 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
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the D-Link router model
    Log into the router web interface or check the physical device label for the exact model number (DI-604, DI-614+, or DI-624)
    Affected if The model is DI-604, DI-614+, or DI-624
  2. Check the firmware version
    Access the router administration page, typically at 192.168.0.1, and navigate to the System or Administration section to view the firmware version
    Affected if The firmware version is 2.30 for DI-614+, 1.28 for DI-624, or any version for DI-604 (all versions affected)
  3. Confirm DHCP server is enabled
    In the router web interface, go to the DHCP settings page and verify if the DHCP server is turned on
    Affected if DHCP server is enabled - the vulnerability requires the DHCP server to be active to be exploitable

The device is affected if it is a DI-604 (any firmware), DI-614+ running firmware 2.30, or DI-624 running firmware 1.28, with the DHCP server feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update router firmware to a version newer than 2.30 if available; if no firmware update exists, replace the end-of-life device with a supported router.

Fix this in Di 604 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2004-0661 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2004-0661 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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