CVE-2002-1623 json
The design of the Internet Key Exchange (IKE) protocol, when using Aggressive Mode for shared secret authentication, does not encrypt initi…
published 2002-12-31 23 y ago modified 2026-06-16 4 mo ago also EUVD-2002-1604
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 48.6%
- EPSS 48.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
The design of the Internet Key Exchange (IKE) protocol, when using Aggressive Mode for shared secret authentication, does not encrypt initiator or responder identities during negotiation, which may allow remote attackers to determine valid usernames by (1) monitoring responses before the password is supplied or (2) sniffing, as originally reported for FireWall-1 SecuRemote.
Exploit prediction
48.57% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- securityfocus.com http://www.securityfocus.com/archive/1/290202 referenced PoC, tagged "exploit" by a source, unverified
- securiteam.com http://www.securiteam.com/securitynews/5TP040U8AW.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
References
-
securityfocus.com
/archive/1/290202
mailing-list, exploit
-
securiteam.com
/securitynews/5TP040U8AW.html
exploit
-
lists.grok.org.uk
/pipermail/full-disclosure/2002-September/001223.html
mailing-list
-
marc.info
/?l=bugtraq&m=103176164729351&w=2
mailing-list
-
securityfocus.com
/bid/5607
vdb-entry
-
kb.cert.org
/vuls/id/886601
third-party-advisory, us-government-resource
- nta-monitor.com /news/checkpoint.htm
- checkpoint.com /techsupport/alerts/ike.html
-
marc.info
/?l=bugtraq&m=103124812629621&w=2
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/10034
vdb-entry
Sources
- CVE List CVE-2002-1623
- NVD CVE-2002-1623
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.