CVE-2002-1623

NONECVSS 0.0Elevated
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 49%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
98.7%
KEV
Not listed

Published

December 31, 2002

Last Modified

June 16, 2026

References (20)

Data Freshness Timeline

(refreshed 4× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 06:07 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-11 08:22 UTCEPSS rescore
  4. 2026-07-08 15:09 UTCEPSS rescore
  5. 2026-07-02 14:00 UTCEPSS rescore
  6. 2026-06-29 14:02 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-28 04:52 UTCEPSS rescore
  9. 2026-06-27 03:04 UTCEPSS rescore
  10. 2026-06-23 21:29 UTCEPSS rescore
  11. 2026-06-21 01:56 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-16 17:49 UTCEPSS rescore
  18. 2026-06-15 17:43 UTCEPSS rescore
  19. 2026-06-14 23:13 UTCEPSS rescore
  20. 2026-06-14 23:13 UTCEPSS rescore
  21. 2026-06-13 22:56 UTCEPSS rescore
  22. 2026-06-12 23:08 UTCEPSS rescore
  23. 2026-06-11 13:55 UTCEPSS rescore
  24. 2026-06-10 22:13 UTCEPSS rescore
  25. 2026-06-10 13:17 UTCEPSS rescore
Show 25 more
  1. 2026-06-08 14:13 UTCEPSS rescore
  2. 2026-06-07 15:21 UTCEPSS rescore
  3. 2026-06-05 22:43 UTCEPSS rescore
  4. 2026-06-05 22:43 UTCEPSS rescore
  5. 2026-06-05 06:07 UTCEPSS rescore
  6. 2026-06-04 13:09 UTCEPSS rescore
  7. 2026-06-02 20:10 UTCEPSS rescore
  8. 2026-06-01 13:49 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-05-31 18:33 UTCEG score recompute
  11. 2026-05-31 18:33 UTCGHSA enrichment
  12. 2026-05-31 00:13 UTCEPSS rescore
  13. 2026-05-31 00:13 UTCEPSS rescore
  14. 2026-05-29 13:40 UTCEPSS rescore
  15. 2026-05-29 13:40 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-27 13:37 UTCEPSS rescore
  20. 2026-05-24 16:42 UTCEPSS rescore
  21. 2026-05-20 22:36 UTCEPSS rescore
  22. 2026-05-20 11:20 UTCEPSS rescore
  23. 2026-05-20 11:20 UTCEPSS rescore
  24. 2026-05-18 21:29 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore

Frequently asked(4)

What is CVE-2002-1623?
CVE-2002-1623 is a none vulnerability published on December 31, 2002. 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…
When was CVE-2002-1623 disclosed?
CVE-2002-1623 was first published in the National Vulnerability Database on December 31, 2002, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2002-1623 actively exploited?
CVE-2002-1623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2002-1623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-1623, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2002-1623

Explore →

Is Your Infrastructure Affected by CVE-2002-1623?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs