What is CVE-2002-20001?A high-severity flaw in Dheater, explained.
CVE-2002-20001 is a high-severity flaw (CVSS 7.5) in Dheater from Balasys, published on 11 November 2021. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 25%. If you run an affected version, plan in the vendor’s fix.
Published 11 November 2021. Record last updated 22 August 2025. We keep this page's data up to date.
What is CVE-2002-20001? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
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.
What kind of flaw is it?
- CWE-400Uncontrolled Resource Consumption
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2002-20001 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 25%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Exploit likelihood fell
- Exploit likelihood jumped
- Record last updated
CVE-2002-20001 scores 52. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2002-20001 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2002-20001? 30 products.
The published record lists 30 products from 6 vendors. Versions are shown as published: "10.06.0000 to before 10.06.0180" means from 10.06.0000 up to, but not including, 10.06.0180. If you run one of these, check your version, then go to the fix below.
- Application
Dheater
by Balasys
Affected versionsversion not specified - Operating system
F5os-C
by F5
Affected versions1.3.0 to 1.3.21.5.01.5.11.6.0 to 1.6.21.8.01.8.1 - Operating system
Arubaos-Cx
by HPE
Affected versions10.06.0000 to before 10.06.018010.07.0000 to before 10.07.003010.08.0000 to before 10.08.001010.09.0000 to before 10.09.0002 - Operating system
F5os-a
by F5
Affected versions1.3.0 to 1.3.21.5.0 to 1.5.31.8.0 - Operating system
Linux Enterprise Server
by Suse
Affected versions111215 - Application
Big-IP Access Policy Manager
by F5
Affected versions13.1.0 to before 16.1.417.0.0 to before 17.1.0 - Application
Big-IP Advanced Firewall Manager
by F5
Affected versions13.1.0 to 17.1.217.5.0 - Application
Big-IP Advanced Web Application Firewall
by F5
Affected versions13.1.0 to 17.1.217.5.0 - Application
Big-IP Analytics
by F5
Affected versions13.1.0 to 17.1.217.5.0
How do I fix CVE-2002-20001? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2002-20001 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The Diffie-Hellman Key Agreement Protocol allows remote attackers (from the client side) to send arbitrary numbers that are actually not public keys, and tri...
- Matched to
- Dheater on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2002-20001 is a high-severity flaw in Dheater from Balasys, published on 11 November 2021. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2002-20001 is 52 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 25%. That can change at any time, which is why we keep watching.
For Dheater from Balasys: version not specified. The record lists 30 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.