Fm114pHardware / appliance · Netgear

CVE-2002-2355

HIGH · 7.1 CVSS v2.0 Published 2002-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 FM114P firmware 1.3 wireless firewall, when configured to backup configuration information, stores DDNS (DynDNS) user name and password, MAC address filtering table and possibly other information in cleartext, which could allow local users to obtain sensitive information.

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 FM114P wireless firewall firmware 1.3 stores sensitive configuration data including DDNS username/password and MAC address filtering tables in cleartext within the configuration backup file, allowing local users with file access to retrieve these credentials.

MitigationSince this is a firmware vulnerability in discontinued 2002-era hardware with no patch available, organizations should retire and replace affected devices, or avoid using the configuration backup feature if the device must remain in service.

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
Fm114pHardware / 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
M
Authentication
None
Confidentiality
Complete
Integrity
None
Availability
None

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

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 Netgear FM114P device in inventory
    Review hardware asset inventory or physically inspect network devices to determine if a Netgear FM114P wireless firewall is deployed
    Affected if The device model is FM114P and firmware version 1.3 is in use
  2. Locate configuration backup file
    Access the device web interface or administrative console and locate the configuration backup/export feature, typically found under Administration or Maintenance settings
    Affected if A configuration backup file exists for this device
  3. Examine backup file for cleartext credentials
    Open the downloaded configuration backup file in a text editor and search for plain text strings resembling DDNS usernames, passwords, or MAC address entries
    Affected if The backup file contains readable DDNS username/password pairs or MAC address filtering tables without encryption
  4. Verify backup file format
    Confirm the backup file is not encrypted by checking if it opens directly as plain text and contains configuration parameters in human-readable form
    Affected if The configuration file is stored in cleartext rather than encrypted format

A user is affected if they operate a Netgear FM114P device and possess a configuration backup file that reveals DDNS credentials or MAC filtering rules in plain text.

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

Since this is a firmware vulnerability in discontinued 2002-era hardware with no patch available, organizations should retire and replace affected devices, or avoid using the configuration backup feature if the device must remain in service.

Fix this in Fm114p Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-2355 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-2355 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