{"vulnerability": "CVE-2002-20001", "sightings": [{"uuid": "05de037f-5e72-4fe7-b5a3-508f554c7dca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "published-proof-of-concept", "source": "Telegram/Fl_ltFZIbiQsMNPTYivk2KXEOFXqbKjLz4yAp3sglbIHJYU", "content": "", "creation_timestamp": "2025-07-28T15:00:06.000000Z"}, {"uuid": "26be3ac8-fd36-451d-a460-7021ed211f51", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "seen", "source": "https://t.me/cibsecurity/32258", "content": "\u203c CVE-2002-20001 \u203c\n\nThe 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)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.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2021-11-11T22:37:55.000000Z"}, {"uuid": "b11b1c1a-1ce2-4188-a3fb-3e3bf6a7b8e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityTechnologies/5006", "content": "#tools\nD(HE)ater is a PoC implementation of the D(HE)at attack (CVE-2002-20001) through which DoS can be performed by enforcing the DHE key exchange\nhttps://github.com/Balasys/dheater", "creation_timestamp": "2021-12-19T13:30:32.000000Z"}, {"uuid": "8d388205-c90a-4d6c-b287-c576fe85e026", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "seen", "source": "https://t.me/GithubRedTeam/88658", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #GitLab #CVE #POC\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a dheater\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a c0r0n3r\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a Python\n\u2b50 Star\u6570\u91cf\uff1a 216  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 30\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-06-13 15:02:58\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nD(HE)ater is a proof of concept implementation of the D(HE)at  attack (CVE-2002-20001) through which denial-of-service can be performed by enforcing the Diffie-Hellman key exchange. (read-only clone of the original GitLab project)\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-07-13T22:00:43.235104Z"}, {"uuid": "0c62cf8d-83f1-4f71-9a71-4c012b5a1278", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "seen", "source": "https://t.me/GithubRedTeam/88658", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #GitLab #CVE #POC\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a dheater\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a c0r0n3r\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a Python\n\u2b50 Star\u6570\u91cf\uff1a 216  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 30\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-06-13 15:02:58\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nD(HE)ater is a proof of concept implementation of the D(HE)at  attack (CVE-2002-20001) through which denial-of-service can be performed by enforcing the Diffie-Hellman key exchange. (read-only clone of the original GitLab project)\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-07-14T00:00:42.391601Z"}, {"uuid": "b3885556-3fda-4062-80f7-fbc7ea1e4345", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/88658", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #GitLab #CVE #POC\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a dheater\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a c0r0n3r\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a Python\n\u2b50 Star\u6570\u91cf\uff1a 216  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 30\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-06-13 15:02:58\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nD(HE)ater is a proof of concept implementation of the D(HE)at  attack (CVE-2002-20001) through which denial-of-service can be performed by enforcing the Diffie-Hellman key exchange. (read-only clone of the original GitLab project)\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-07-15T00:00:05.908990Z"}, {"uuid": "627e2f3a-6304-4758-af39-b767466600d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "seen", "source": "https://t.me/hacking_Attack/74815", "content": "Black Hat Ethical Hacking\nOpenSSL Gives Heads Up to Critical Vulnerability Disclosure\n\nOpenSSL Gives Heads Up to Critical Vulnerability DisclosurePost Views: 66 Premium Contenthttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/09/Patreon.png Subscribe to Patreon to watch this episode.\nReading Time: 3 Minutes Developers of the OpenSSL\u00a0cryptography\u00a0library have taken the unusual step of pre-warning that an update due to land next Tuesday (November 1) will fix a critical vulnerability.The looming OpenSSL 3.x patch represent only the second time the project has addressed a flaw classified as \u2018critical\u2019. The only previous OpenSSL update of such elevated severity addressed the infamous Heartbleed vulnerability (CVE-2014-0160).\n\nHeartbleed was a memory handling bug that opened the door for attackers to access secret keys, passwords, and sensitive personal information from vulnerable servers. At the time of its discovery eight years ago, experts from Netcraft estimated that the flaw affected 17% of SSL web servers or \u201chalf a million widely trusted websites\u201d.\n\nLittle is known about the upcoming critical fix (OpenSSL 3.0.7), other than it is restricted to OpenSSL version 3.0, the latest release line of the software, and does not affect previous versions.\n\nOpenSSL 3.0.x only debuted in 2021, a factor that might limit the extent of the problems next week\u2019s announcement will reveal. OpenSSL has been around since 1998 and most systems today are still built using earlier release lines.\n\nNo details of the upcoming patch or the critical flaw it tackles have been released. In the absence of any hard info, infosec Twitter has gone into overdrive with some speculating that the vulnerability might represent the \u201cnext Heartbleed\u201d.\n\nOne security expert from Google, for example, has suggested\u00a0on the basis of recent software commits and a blog post by the OpenSSL team that the update might relate to a denial-of-service (DoS) issue.\nSee Also: So you want to be a hacker? Complete Offensive Security and Ethical Hacking Course Feel the DHEatThis particular DoS bug \u2013 known as DHEat and previous confirmed to affect OpenVPN and SSH services \u2013 involves enforcing the Diffie-Hellman key exchange.\n\nDHEat (AKA CVE-2002-20001) scores 7.5 on the CVSS 3.1 index, indicating high severity and falling somewhat short of critical.\n\nOn the face of it, an OpenSSL patch for DHEat would appear to be a poor candidate for a critical patch unless OpenSSL is particularly vulnerable. A recent OpenSSL blog post\u00a0referencing DHEat makes it even more unlikely that the looming patch tackles this issue.\n\nIt seems more likely that a previously unknown vulnerability is at play, according to experts quizzed by The Daily Swig.\nTrending: Exploit XSS Injections in a one-line powerful Technique\nTrending: Recon Tool: Hakrawler Action stationsBrian Fox, CTO of Sonatype, told us\u00a0that organizations should audit their code base for exposure to any vulnerability in OpenSSL 3.0.x, leaving them prepared to either patch or isolate vulnerable systems next week.\n\n\u201cIn the first instance, it\u2019s critical to find out where 3.x is used,\u201d Fox said. \u201cMore importantly, it\u2019s vital to get tooling in place to avoid having to audit and identify components manually every time.\u201d\n\nFox went on to argue that speculation about the content of the upcoming fix were, at best, \u201cunhelpful\u201d. He said: \u201cThe speculation assumes that the fix is available in the publicly visible source and the advance notice gives attackers time to find it. This assumption may not be true. It is a best practice at some times to embargo the actual change until after the announcement for this exact reason.\n\n\u201cThe team at OpenSSL consists of some of the foremost experts in handling high profile open sou[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-01T20:01:19.531364Z"}, {"uuid": "afd093ba-6a11-43e1-8d46-cf1b91b0b077", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2002-20001", "type": "seen", "source": "https://t.me/hacking_Attack/74815", "content": "Black Hat Ethical Hacking\nOpenSSL Gives Heads Up to Critical Vulnerability Disclosure\n\nOpenSSL Gives Heads Up to Critical Vulnerability DisclosurePost Views: 66 Premium Contenthttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/09/Patreon.png Subscribe to Patreon to watch this episode.\nReading Time: 3 Minutes Developers of the OpenSSL\u00a0cryptography\u00a0library have taken the unusual step of pre-warning that an update due to land next Tuesday (November 1) will fix a critical vulnerability.The looming OpenSSL 3.x patch represent only the second time the project has addressed a flaw classified as \u2018critical\u2019. The only previous OpenSSL update of such elevated severity addressed the infamous Heartbleed vulnerability (CVE-2014-0160).\n\nHeartbleed was a memory handling bug that opened the door for attackers to access secret keys, passwords, and sensitive personal information from vulnerable servers. At the time of its discovery eight years ago, experts from Netcraft estimated that the flaw affected 17% of SSL web servers or \u201chalf a million widely trusted websites\u201d.\n\nLittle is known about the upcoming critical fix (OpenSSL 3.0.7), other than it is restricted to OpenSSL version 3.0, the latest release line of the software, and does not affect previous versions.\n\nOpenSSL 3.0.x only debuted in 2021, a factor that might limit the extent of the problems next week\u2019s announcement will reveal. OpenSSL has been around since 1998 and most systems today are still built using earlier release lines.\n\nNo details of the upcoming patch or the critical flaw it tackles have been released. In the absence of any hard info, infosec Twitter has gone into overdrive with some speculating that the vulnerability might represent the \u201cnext Heartbleed\u201d.\n\nOne security expert from Google, for example, has suggested\u00a0on the basis of recent software commits and a blog post by the OpenSSL team that the update might relate to a denial-of-service (DoS) issue.\nSee Also: So you want to be a hacker? Complete Offensive Security and Ethical Hacking Course Feel the DHEatThis particular DoS bug \u2013 known as DHEat and previous confirmed to affect OpenVPN and SSH services \u2013 involves enforcing the Diffie-Hellman key exchange.\n\nDHEat (AKA CVE-2002-20001) scores 7.5 on the CVSS 3.1 index, indicating high severity and falling somewhat short of critical.\n\nOn the face of it, an OpenSSL patch for DHEat would appear to be a poor candidate for a critical patch unless OpenSSL is particularly vulnerable. A recent OpenSSL blog post\u00a0referencing DHEat makes it even more unlikely that the looming patch tackles this issue.\n\nIt seems more likely that a previously unknown vulnerability is at play, according to experts quizzed by The Daily Swig.\nTrending: Exploit XSS Injections in a one-line powerful Technique\nTrending: Recon Tool: Hakrawler Action stationsBrian Fox, CTO of Sonatype, told us\u00a0that organizations should audit their code base for exposure to any vulnerability in OpenSSL 3.0.x, leaving them prepared to either patch or isolate vulnerable systems next week.\n\n\u201cIn the first instance, it\u2019s critical to find out where 3.x is used,\u201d Fox said. \u201cMore importantly, it\u2019s vital to get tooling in place to avoid having to audit and identify components manually every time.\u201d\n\nFox went on to argue that speculation about the content of the upcoming fix were, at best, \u201cunhelpful\u201d. He said: \u201cThe speculation assumes that the fix is available in the publicly visible source and the advance notice gives attackers time to find it. This assumption may not be true. It is a best practice at some times to embargo the actual change until after the announcement for this exact reason.\n\n\u201cThe team at OpenSSL consists of some of the foremost experts in handling high profile open sou[...]\n\n___________________________ \n@hacking_Attack\n@Hacking_Video", "creation_timestamp": "2026-09-02T01:01:34.465633Z"}]}