dbcve.org
Vpn 3000 Concentrator Series SoftwareOperating system · Cisco

CVE-2002-1094

MEDIUM · 5.0 CVSS v2.0 Published 2002-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Information leaks in Cisco VPN 3000 Concentrator 2.x.x and 3.x.x before 3.5.4 allow remote attackers to obtain potentially sensitive information via the (1) SSH banner, (2) FTP banner, or (3) an incorrect HTTP request.

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 confidence

The Cisco VPN 3000 Concentrator versions 2.x.x and 3.x.x before 3.5.4 expose potentially sensitive system information through multiple vectors: SSH banner, FTP banner, and incorrect HTTP requests. This information disclosure could aid attackers in reconnaissance or identifying vulnerable configurations.

MitigationUpgrade the Cisco VPN 3000 Concentrator firmware to version 3.5.4 or later to remediate the information disclosure vulnerability.

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
Vpn 3000 Concentrator Series SoftwareOperating system
Affected:= 2.0= 2.5.2.a= 2.5.2.b= 2.5.2.c= 2.5.2.d= 2.5.2.f= 3.0= 3.0\(rel\)= 3.0.3.a= 3.0.3.b= 3.0.4= 3.1\(rel\)
Vpn 3002 Hardware ClientApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the VPN Concentrator firmware version
    Access the device console or admin interface and navigate to Administration > System Summary or use the 'show version' command via console/SSH to retrieve the running firmware version.
    Affected if The installed version is 2.0, 2.5.2.a, 2.5.2.b, 2.5.2.c, 2.5.2.d, 2.5.2.f, 3.0, 3.0(rel), 3.0.3.a, 3.0.3.b, 3.0.4, 3.1(rel), or any version prior to 3.5.4, or if the device is a VPN 3002 Hardware Client (all versions are affected).
  2. Verify if SSH access is enabled
    Check the device configuration under Administration > Access Settings > SSH to confirm whether the SSH service is active.
    Affected if SSH is enabled and connects to the device to observe whether the SSH banner reveals system information such as software version, build number, or internal configuration details.
  3. Verify if FTP access is enabled
    Check the device configuration under Administration > Access Settings > FTP to confirm whether the FTP service is active.
    Affected if FTP is enabled and connects to the device to observe whether the FTP banner reveals system information such as software version, hostname, or device model details.
  4. Verify if HTTP management interface is enabled
    Check the device configuration under Administration > Access Settings > HTTP to confirm whether the web-based management interface is active.
    Affected if HTTP is enabled and sending malformed or unexpected HTTP requests to the device reveals version information, directory paths, or other system details in error messages or responses.

The environment is affected if the Cisco VPN 3000 Concentrator runs firmware version 3.5.3 or earlier (or is a VPN 3002 Hardware Client of any version) AND has SSH, FTP, or HTTP services enabled that expose system information in their banners or error responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Cisco VPN 3000 Concentrator firmware to version 3.5.4 or later to remediate the information disclosure vulnerability.

Fix this in Vpn 3000 Concentrator Series Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-1094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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