CVE-2002-2020
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 · uneditedNetgear RP114 Cable/DSL Web Safe Router Firmware 3.26 uses a default administrator password and accepts admin logins on the external interface, which allows remote attackers to gain privileges if the password is not changed.
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 Netgear RP114 Cable/DSL Web Safe Router firmware 3.26 ships with a default administrator password and exposes the administrative login interface on the external/public network interface. This allows any remote attacker with network access to the router's external IP to authenticate using the well-known default credentials and gain full administrative control over the device.
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= 3.26CVSS 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 modelLog into the router admin interface or physically inspect the device to confirm it is a Netgear RP114. The model number is typically displayed on the device label or in the web admin interface header.Affected if The device is a Netgear RP114 router.
-
Check the firmware versionAccess the router web admin interface (typically at 192.168.0.1 or similar LAN IP) and navigate to the firmware or status page to view the installed firmware version.Affected if The firmware version is exactly 3.26.
-
Verify admin interface is exposed on WANFrom an external network (not on the LAN), attempt to access the router login page using the public/WAN IP address on the standard HTTP port (80). This can be done by entering the router's external IP in a web browser from outside the local network.Affected if The router login page is accessible from the public/WAN IP address on port 80.
-
Test default credentialsAttempt to log in to the router admin interface using the well-known default credentials for this device. The default username is typically 'admin' and the default password is '1234' for the Netgear RP114 3.26 firmware.Affected if Authentication succeeds with the default username/password combination.
The environment is affected if a Netgear RP114 router running firmware 3.26 has its admin interface exposed on the WAN and still uses the default password.
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 dataImmediately change the default administrator password to a strong, unique password and disable external administrative access by restricting the admin interface to the internal LAN only, or use firewall rules to block external admin access.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2020 — 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-2002-2020 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