dbcve.org
Linksys Wrt350nHardware / appliance · Cisco

CVE-2008-4296

HIGH · 10.0 CVSS v2.0 Published 2008-09-27
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
The Cisco Linksys WRT350N with firmware 1.0.3.7 has "admin" as its default password for the "admin" account, which makes it easier for remote attackers to obtain access.

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 Cisco Linksys WRT350N router firmware 1.0.3.7 ships with a hardcoded default credential of 'admin' for the administrator account. Remote attackers can trivially authenticate to the device's web management interface using these known default credentials, gaining full administrative control over the router.

MitigationImmediately change the default 'admin' password to a strong, unique password via the router's web administration interface. If the device is no longer supported with firmware updates, consider replacing it with a current model.

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
Linksys Wrt350nHardware / 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 router model
    Check the device label on the bottom of the router or log into the web interface and look for the model number in the status or firmware section
    Affected if The device is a Cisco Linksys WRT350N router
  2. Determine if remote web management is enabled
    Log into the router web interface, navigate to Administration > Remote Management, and check if remote management access is allowed from the WAN/internet
    Affected if Remote management is enabled and accessible from the internet
  3. Test default credential authentication
    Attempt to access the router's web management interface using a browser. When prompted for credentials, enter username 'admin' and password 'admin', or try other common default passwords for Linksys devices
    Affected if Authentication succeeds with the default 'admin'/'admin' credentials or other known default passwords
  4. Verify password has been changed
    If you have administrator access, navigate to the Administration > Management section in the web interface and confirm the admin account password is not set to the default 'admin' value
    Affected if The password is still set to the default 'admin' value or has never been changed from factory defaults

A user is affected if they own a Cisco Linksys WRT350N router that still has the default administrator password 'admin' configured, especially if remote web management is 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.

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

Immediately change the default 'admin' password to a strong, unique password via the router's web administration interface. If the device is no longer supported with firmware updates, consider replacing it with a current model.

Recommended fix High confidence
  1. Log into the Linksys WRT350N router web interface using the default credentials (admin/admin)
  2. Navigate to the Administration or Management section of the router settings
  3. Locate the password change option for the admin account
  4. Change the default password from 'admin' to a strong, unique password that meets the router's complexity requirements
  5. Save the settings and restart the router
  6. Verify that the new password is required for future access to the router interface
  7. If available, check Cisco/Linksys support for any firmware updates that may address this vulnerability and apply them

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

Fix this in Linksys Wrt350n Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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