CVE-2002-1937
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 · uneditedSymantec Firewall/VPN Appliance 100 through 200R hardcodes the administrator's MAC address inside the firewall's configuration, which allows remote attackers to spoof the administrator's MAC address and perform an ARP poisoning man-in-the-middle attack to obtain the administrator's password.
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 Symantec Firewall/VPN Appliance 100 through 200R stores the administrator's MAC address in plaintext within the firewall's configuration file. Attackers can spoof this MAC address and perform ARP poisoning man-in-the-middle attacks to intercept and capture the administrator's authentication credentials.
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 dataall versionsall versionsall versionsCVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the appliance modelLog into the appliance or check hardware labeling to confirm the exact model is a Symantec Firewall/VPN Appliance 100, 200, or 200RAffected if The model is any of these three appliances (100, 200, or 200R)
-
Locate the configuration fileAccess the appliance's configuration backup or configuration file. On this appliance line, configuration files are typically exported via the web management interface or CLI using 'show config' or 'backup' commandsAffected if You can access a configuration export from the appliance
-
Search for MAC address entriesOpen the configuration file and search for strings containing MAC address format (XX:XX:XX:XX:XX:XX or XX-XX-XX-XX-XX-XX) in plaintext, particularly entries labeled as admin, administrator, or management MACAffected if A plaintext MAC address appears in the configuration file associated with admin or management roles
-
Check management interface exposureVerify if the appliance's management interface (HTTP/HTTPS admin web UI or management VLAN) is accessible from untrusted networks or the internetAffected if The management interface is reachable from networks outside the trusted internal network
If you are running a Symantec Firewall/VPN Appliance 100, 200, or 200R and its configuration file contains a plaintext administrator MAC address accessible to potential attackers on your network, you are affected by this vulnerability.
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 dataContact Symantec for available firmware updates or patches that remove hardcoded MAC addresses. If no update exists, implement network segmentation to isolate the management interface and consider replacing the end-of-life appliance with a supported solution.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1937 — 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-1937 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