Vpn 3000 Concentrator Series SoftwareOperating system · Cisco
CVE-2002-1092
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 · uneditedCisco VPN 3000 Concentrator 3.6(Rel) and earlier, and 2.x.x, when configured to use internal authentication with group accounts and without any user accounts, allows remote VPN clients to log in using PPTP or IPSEC user authentication.
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 Cisco VPN 3000 Concentrator versions 3.6(Rel) and earlier, as well as 2.x.x, contains an authentication bypass vulnerability when configured to use internal authentication with group accounts but no individual user accounts. In this configuration, remote VPN clients can successfully authenticate using PPTP or IPSEC user authentication credentials, granting unauthorized access to the VPN. This occurs because the concentrator incorrectly processes user-level authentication attempts when only group-level accounts exist in the internal database.
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
<= 3.6\(rel\)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 checksWork through these to decide whether this CVE applies to you.
-
Verify VPN Concentrator software versionAccess the device management interface or use 'show version' command to retrieve the installed software version. Compare against the affected range: versions 3.6(Rel) and earlier, including all 2.x.x versions.Affected if Running version 3.6(Rel) or earlier, or any 2.x.x version
-
Confirm internal authentication is enabledNavigate to Authentication > Configuration in the VPN 3000 management interface or use 'show authentication' command to check if Internal Database is selected as the authentication server.Affected if Internal authentication database is configured as the primary authentication method
-
Inspect internal user database for account typesAccess the User Management or Internal Database section in the device management interface. Review the configured accounts to determine if only group accounts exist with no individual user accounts defined.Affected if Group accounts are present but no individual user accounts are configured
-
Check for PPTP or IPSec user authentication enablementReview the VPN client configuration or tunnel settings in the device management interface under PPP/IPSEC configuration sections. Determine if PPTP or IPSec user-level authentication methods are permitted for client connections.Affected if PPTP or IPSec user authentication is enabled and permitted for remote client connections
A system is affected if it is running version 3.6(Rel) or earlier, uses internal authentication with group-only accounts (no individual users), and allows PPTP or IPSec user authentication, enabling unauthorized VPN access.
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 dataAdd at least one individual user account to the internal authentication database, or upgrade to a version beyond 3.6(Rel) that addresses this vulnerability. Alternatively, review and enforce proper group vs. user authentication policies to ensure only intended authentication methods are permitted.
Fix this in Vpn 3000 Concentrator Series Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1092 — 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-1092 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