CVE-2002-0782
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 · uneditedNovell BorderManager 3.5 with PAT (Port-Address Translate) enabled allows remote attackers to cause a denial of service by filling the connection table with a large number of connection requests to hosts that do not have a specific route, which may be forwarded to the public interface.
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 confidenceNovell BorderManager 3.5 with PAT (Port-Address Translate) enabled contains a resource exhaustion vulnerability. Remote attackers can cause denial of service by flooding the connection table with numerous connection requests to hosts without specific routes, which get forwarded to the public interface, overwhelming the system.
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.5CVSS 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
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Confirm Novell BorderManager 3.5 is installedCheck the installed version of Novell BorderManager on the system using the Novell installer or product information utility. Compare the version number to 3.5.Affected if The installed version is Novell BorderManager 3.5 exactly.
-
Verify PAT feature is enabledAccess the BorderManager administration console or configuration interface and check whether Port-Address Translation (PAT) is turned on in the proxy/NAT settings.Affected if PAT is enabled in the BorderManager configuration.
-
Review connection table for exhaustion symptomsUse the BorderManager management tools or command line utilities to view the current connection table size and utilization. Look for entries approaching or hitting the maximum connection limit.Affected if The connection table is approaching capacity with many pending or incomplete connections to external IP addresses.
-
Check for connections to unroutable hostsInspect the connection table or proxy logs for patterns of connection requests to external IP addresses that do not have specific routes defined, which would be forwarded to the public interface.Affected if There are numerous connection attempts to hosts without specific routes in the connection table.
If Novell BorderManager 3.5 is running with PAT enabled and the connection table is saturated with requests to unroutable hosts being forwarded to the public interface, the environment is 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 dataDisable PAT if not required, or implement connection rate limiting/throttling on the proxy to prevent connection table exhaustion from excessive requests.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0782 — 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-0782 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