dbcve.org
Vpn 3000 Concentrator Series SoftwareOperating system · Cisco

CVE-2002-1098

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
Cisco VPN 3000 Concentrator 2.2.x, and 3.x before 3.5.3, adds an "HTTPS on Public Inbound (XML-Auto)(forward/in)" rule but sets the protocol to "ANY" when the XML filter configuration is enabled, which ultimately allows arbitrary traffic to pass through the concentrator.

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.2.x and 3.x prior to 3.5.3 have a flaw in the XML filter configuration. When enabled, the XML filter adds an 'HTTPS on Public Inbound' rule but incorrectly sets the protocol to 'ANY' instead of restricting it to HTTPS only. This misconfiguration allows arbitrary traffic of any protocol to pass through the VPN concentrator, bypassing the intended security controls and exposing internal resources.

MitigationUpgrade the Cisco VPN 3000 Concentrator to version 3.5.3 or later, which contains the fix for the XML filter protocol misconfiguration. After upgrading, verify that the filter rule correctly restricts traffic to HTTPS only.

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

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

  1. Identify device model and software version
    Access the VPN 3000 Concentrator management interface or CLI and retrieve the system software version information. For the management interface, go to Administration > Session Management > Sessions or use 'show version' in CLI.
    Affected if The device is a Cisco VPN 3000 Concentrator (model 3005, 3015, 3030, 3060, or 3080) or VPN 3002 Hardware Client running version 2.0, 2.5.2.a-f, 3.0, 3.0(rel), 3.0.3.a-b, 3.0.4, or 3.1.
  2. Confirm XML filter feature is enabled
    Navigate to the VPN 3000 management interface and check Configuration > Policy Management > XML Filter or locate the XML filter settings. In CLI, look for XML filter configuration.
    Affected if The XML filter feature is currently enabled on the device.
  3. Inspect the HTTPS on Public Inbound filter rule
    In the XML filter configuration, locate the rule named 'HTTPS on Public Inbound' or similar. Examine the protocol setting for this rule - check whether it shows 'ANY' or 'HTTPS' (or TCP port 443) as the permitted protocol.
    Affected if The rule exists and the protocol field is set to 'ANY' instead of being restricted to HTTPS only.

A user is affected if they are running an affected Cisco VPN 3000 Concentrator or 3002 version with the XML filter enabled and the 'HTTPS on Public Inbound' rule configured with protocol set to 'ANY'.

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 to version 3.5.3 or later, which contains the fix for the XML filter protocol misconfiguration. After upgrading, verify that the filter rule correctly restricts traffic to HTTPS only.

Fix this in Vpn 3000 Concentrator Series Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1098 — 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-1098 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