dbcve.org
Wgt624Hardware / appliance · Netgear

CVE-2006-1002

HIGH · 10.0 CVSS v2.0 Published 2006-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
NETGEAR WGT624 Wireless DSL router has a default account of super_username "Gearguy" and super_passwd "Geardog", which allows remote attackers to modify the configuration. NOTE: followup posts have suggested that this might not occur with all WGT624 routers.

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

The NETGEAR WGT624 Wireless DSL router ships with a hardcoded administrative account (super_username 'Gearguy' and super_passwd 'Geardog') that cannot be changed through the web interface. Remote attackers with network access to the router can use these default credentials to gain full administrative control and modify device configuration.

MitigationImmediately change the default credentials if the device supports it, or replace the device with a model that allows credential changes, as this hardcoded account poses a critical authentication bypass risk.

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
Wgt624Hardware / appliance
Affected:all versions

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 device model
    Check the device label, MAC address (Netgear OUI prefix 00:09:5B or similar), or log into the router web interface to confirm the model is Netgear WGT624
    Affected if The device is a Netgear WGT624 router
  2. Check if router web interface is accessible
    Access the router IP address on common ports (80, 443, 8080) from the network to verify the management interface is reachable
    Affected if The web management interface is exposed on the network
  3. Test hardcoded credentials for login
    Attempt to log into the router web interface using username 'Gearguy' and password 'Geardog'
    Affected if The login succeeds with these hardcoded credentials, confirming the default account is active
  4. Verify if hardcoded credentials can be changed
    In the router administration settings, look for user account management or password change options and attempt to modify the Gearguy account credentials
    Affected if The Gearguy account credentials cannot be changed or are not present in the configurable user list, indicating the hardcoded account persists
  5. Check for remote management exposure
    Determine if remote management or WAN access is enabled on the router (check 'Remote Management' or 'Access Control' settings)
    Affected if Remote management is enabled and the router is reachable from the WAN, allowing external attackers to attempt the hardcoded credentials

A user is affected if they have a Netgear WGT624 device where the Gearguy/Geardog account is accessible and cannot be changed through the web interface.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change the default credentials if the device supports it, or replace the device with a model that allows credential changes, as this hardcoded account poses a critical authentication bypass risk.

Recommended fix High confidence

Replace with a current NETGEAR router model (e.g., R6700, R7000, or newer) or any actively supported router from a reputable vendor.

  1. 1. Immediately disable remote administration on the WGT624 router if enabled, or disconnect it from the internet.
  2. 2. Replace the NETGEAR WGT624 with a current, supported router model that receives security updates.
  3. 3. After deploying the new router, change all default credentials and ensure remote administration is disabled or restricted by IP address.
Caveat The WGT624 is an end-of-life product from approximately 2002-2004 and no longer receives security updates; replacement is the only viable remediation.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wgt624 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-1002 — 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-2006-1002 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