CVE-2002-0309
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 · uneditedSMTP proxy in Symantec Enterprise Firewall (SEF) 6.5.x includes the firewall's physical interface name and address in an SMTP protocol exchange when NAT translation is made to an address other than the firewall, which could allow remote attackers to determine certain firewall configuration 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 confidenceThe SMTP proxy in Symantec Enterprise Firewall 6.5.x incorrectly includes the firewall's physical interface name and IP address in SMTP traffic during NAT translation to non-firewall addresses, leaking internal network configuration to external attackers.
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= 6.5.2CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Symantec Enterprise Firewall installationLocate and verify the presence of Symantec Enterprise Firewall software on the systemAffected if Symantec Enterprise Firewall is not installed on the system
-
Verify the installed versionCheck the installed version of Symantec Enterprise Firewall and confirm it is exactly 6.5.2Affected if The installed version is 6.5.2 (other versions are not affected)
-
Confirm SMTP proxy is enabledCheck the firewall configuration for SMTP proxy functionality statusAffected if SMTP proxy is enabled in the firewall settings
-
Identify SMTP NAT translation rulesReview NAT configuration to determine if there are rules translating SMTP traffic to non-firewall addressesAffected if NAT rules exist that forward SMTP traffic through the firewall to external destinations
-
Capture and inspect outbound SMTP trafficUse a network sniffer or log analysis to capture SMTP packets traversing the firewall and examine headers for the firewall interface IP or hostnameAffected if The SMTP traffic contains the firewall's physical interface IP address or interface name in the message headers instead of internal client addresses
The environment is affected if Symantec Enterprise Firewall version 6.5.2 is running with the SMTP proxy enabled and NAT rules translating SMTP traffic to external addresses, resulting in internal network information leakage in SMTP headers.
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 dataSince SEF 6.5.x is discontinued, migrate to a supported firewall solution; if immediate migration is not feasible, disable the SMTP proxy functionality or ensure the firewall is not used for SMTP NAT traversal.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0309 — 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-0309 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