nday
CVE-2002-20001

The Diffie-Hellman Key Agreement Protocol allows remote attackers (from the client side) to send…Title composed by nday; the CVE record has none.

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

resource exhaustion
CWE-400, stated by NVD's analysts
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
ArubaOS
CPE names NVD's analysts give as vulnerable: o:hpe:arubaos-cx
F5 BIG-IP
CPE names NVD's analysts give as vulnerable: a:f5:big-ip_access_policy_manager, a:f5:big-ip_advanced_firewall_manager, a:f5:big-ip_advanced_web_application_firewall, a:f5:big-ip_analytics, a:f5:big-ip_application_acceleration_manager, a:f5:big-ip_application_security_manager, a:f5:big-ip_application_visibility_and_reporting, a:f5:big-ip_carrier-grade_nat, a:f5:big-ip_ddos_hybrid_defender, a:f5:big-ip_domain_name_system and 10 more
Siemens SCALANCE
CPE names NVD's analysts give as vulnerable: o:siemens:scalance_w1750d_firmware
router / switch
CPE names NVD's analysts give as vulnerable: a:f5:big-ip_access_policy_manager, a:f5:big-ip_advanced_firewall_manager, a:f5:big-ip_advanced_web_application_firewall, a:f5:big-ip_analytics, a:f5:big-ip_application_acceleration_manager, a:f5:big-ip_application_security_manager, a:f5:big-ip_application_visibility_and_reporting, a:f5:big-ip_carrier-grade_nat, a:f5:big-ip_ddos_hybrid_defender, a:f5:big-ip_domain_name_system and 12 morethe product type of ArubaOS, F5 BIG-IP, and Siemens SCALANCE in nday's product registry
ICS / OT
CPE names NVD's analysts give as vulnerable: o:siemens:scalance_w1750d_firmwarethe product type of Siemens SCALANCE in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2021-11-11T00:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

The Diffie-Hellman Key Agreement Protocol allows remote attackers (from the client side) to send arbitrary numbers that are actually not public keys, and trigger expensive server-side DHE modular-exponentiation calculations, aka a D(HE)at or D(HE)ater attack. The client needs very little CPU resources and network bandwidth. The attack may be more disruptive in cases where a client can require a server to select its largest supported key size. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by mitre.

src cvelist · nday , bulk import · raw
{
  "id": 79389,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2002-20001",
  "occurred_at": "2021-11-11T00:00:00Z",
  "observed_at": "2026-11-13T05:35:36.93775Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2021-11-11T00:00:00.000Z",
    "assigner_short_name": "mitre"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.