CVE-2002-0134
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 · uneditedTelnet proxy in Avirt Gateway Suite 4.2 does not require authentication for connecting to the proxy system itself, which allows remote attackers to list file contents of the proxy and execute arbitrary commands via a "dos" command.
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 Avirt Gateway Suite 4.2 telnet proxy lacks authentication enforcement, allowing unauthenticated remote attackers to connect directly to the proxy service. Attackers can list file contents on the proxy system and execute arbitrary operating system commands through a 'dos' command interface.
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= 4.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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Verify Avirt Gateway Suite 4.2 installationCheck for Avirt Gateway Suite installation by searching for the product directory, examining installed programs list, or querying Windows services for Avirt-related entries. The default installation path may be in Program Files or a custom directory chosen during setup.Affected if Avirt Gateway Suite version 4.2 is found installed on the system
-
Confirm telnet proxy service is runningQuery running services or processes for the Avirt telnet proxy service. Common service names may include 'Avirt Gateway', 'Avirt Telnet Proxy', or similar variations. Use commands like 'sc query' or check the services control panel.Affected if The Avirt telnet proxy service is currently running and accepting connections
-
Test telnet proxy for authentication bypassAttempt to connect to the telnet proxy port (typically port 23 or configured proxy port) from a remote system or localhost using a telnet client without providing any credentials. Observe if the connection is accepted and provides access to the proxy interface.Affected if The telnet proxy accepts connections without requiring authentication credentials
-
Check proxy configuration for authentication enforcementLocate and examine the Avirt Gateway Suite configuration files, typically found in the installation directory. Look for settings related to telnet proxy authentication, such as 'require authentication', 'auth required', or similar configuration parameters.Affected if The configuration shows authentication is disabled or not required for the telnet proxy service
-
Verify command execution interface availabilityIf connected to the proxy without authentication, attempt to use the 'dos' command interface to list files or execute commands. This may involve typing 'dos' or similar commands at the proxy prompt to access the operating system command shell.Affected if The 'dos' command interface is accessible and allows file listing or OS command execution without authentication
The system is affected if Avirt Gateway Suite 4.2 is installed with the telnet proxy service running and accepting unauthenticated connections that allow command execution through the 'dos' interface.
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 dataIf the product is still in use, disable the unauthenticated telnet proxy or upgrade to a supported version with proper authentication controls. Given this is a 2002 vulnerability affecting a legacy product, consider migration to modern secure alternatives.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0134 — 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-0134 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