Vpn ClientApplication · Cisco
CVE-2002-1107
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 Virtual Private Network (VPN) Client software 2.x.x, and 3.x before 3.5.2B, does not generate sufficiently random numbers, which may make it vulnerable to certain attacks such as spoofing.
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 Client software versions 2.x.x and 3.x before 3.5.2B contains a weak random number generator that produces insufficiently random numbers for cryptographic operations. This entropy weakness could allow attackers to predict or guess the random values used in security-critical functions, potentially enabling spoofing attacks against VPN connections.
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 ClientApplication
= 2.0= 3.0= 3.0.5= 3.1= 3.5.1= 3.5.1c= 3.5.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 Cisco VPN Client installationSearch the system for Cisco VPN Client executables (e.g., vpnclient.exe, ipsecdial.exe) or check Add/Remove Programs for Cisco VPN Client entryAffected if The software is present on the system
-
Retrieve installed version informationRight-click the VPN Client executable, select Properties, then view the Version tab to obtain the file version; alternatively, check the Windows Registry under HKLM\SOFTWARE\Cisco Systems for version keysAffected if Version information cannot be retrieved or shows an older release
-
Compare version against affected rangeCompare your installed version to the affected list: version 2.0, 3.0, 3.0.5, 3.1, 3.5.1, 3.5.1c, or 3.5.2; note that any 2.x.x or 3.x version before 3.5.2B is considered vulnerableAffected if Installed version matches any version in the 2.x.x or 3.x line prior to 3.5.2B, specifically any of the listed affected versions
-
Identify cryptographic usage contextCheck if the VPN Client is configured to establish active VPN tunnels or is used for IPsec negotiations; review any logs or active sessions showing active VPN connectionsAffected if The client is actively establishing VPN connections using the vulnerable cryptographic functions
A system is affected if Cisco VPN Client version 2.x or 3.x (specifically versions 2.0, 3.0, 3.0.5, 3.1, 3.5.1, 3.5.1c, or 3.5.2) is installed and actively used for VPN connections.
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 dataUpgrade affected Cisco VPN Client installations to version 3.5.2B or later which contains the proper random number generation fix. For legacy systems that cannot be upgraded, consider compensating controls such as network segmentation or additional authentication layers.
Fix this in Vpn Client
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1107 — 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-1107 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