CVE-2000-0152
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 · uneditedRemote attackers can cause a denial of service in Novell BorderManager 3.5 by pressing the enter key in a telnet connection to port 2000.
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 · moderate confidenceNovell BorderManager 3.5 contains a remote denial of service vulnerability where an attacker can crash the service by establishing a telnet connection to port 2000 and pressing the enter key. This indicates a critical flaw in input handling for the service listening on that port.
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.0= 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 is installedInspect installed programs or check for Novell BorderManager services on the system using system inventory tools or registry queries for Novell softwareAffected if Novell BorderManager software is present on the system
-
Verify the BorderManager versionCheck the installed version of Novell BorderManager through the software's built-in version information or system information utilitiesAffected if The installed version is 3.0 or 3.5 specifically
-
Identify if port 2000 is open and listeningUse a network port scanner (such as netstat, nmap, or similar tools) to determine if port 2000 is in a LISTENING state on the serverAffected if Port 2000 is open and accepting connections
-
Test for service response on port 2000Establish a telnet connection to port 2000 on the target server and observe whether the connection is accepted by a BorderManager serviceAffected if A telnet connection to port 2000 successfully connects to a BorderManager service process
-
Assess network accessibility of port 2000Determine whether port 2000 is exposed to untrusted networks by reviewing firewall rules and network segmentation configurationsAffected if Port 2000 is reachable from network segments that contain untrusted or external users
The environment is affected if Novell BorderManager version 3.0 or 3.5 is installed, the service is running on port 2000, and that port is network-accessible to potential attackers.
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 BorderManager 3.5 is a legacy product from circa 2000, the primary remediation is to upgrade to a supported version or migrate to a modern proxy/ VPN solution, as patches for this version are likely unavailable. If the system cannot be upgraded, network segmentation should be applied to restrict access to port 2000 to trusted sources only.
- 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-2000-0152 — 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-2000-0152 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