CVE-2024-28872 Incorrect TLS certificate validation can lead to escalated privileges
Attackers can bypass TLS validation to send malicious commands to monitored services, causing data loss or denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-28872?
CVE-2024-28872 is a high-severity vulnerability in ISC Stork, published on 11 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The TLS certificate validation code is flawed. An attacker can obtain a TLS certificate from the Stork server and use it to connect to the Stork agent. Once this connection is established with the valid certificate, the attacker can send malicious commands to a monitored service (Kea or BIND 9), possibly resulting in confidential data loss and/or denial of service. It should be noted that this vulnerability is not related to BIND 9 or Kea directly, and only customers using the Stork management tool are potentially affected. This issue affects Stork versions 0.15.0 through 1.15.0.
Weakness: CWE-295
Which versions are affected by CVE-2024-28872?
It affects 1 product.
Products include Isc Stork.
How do I fix CVE-2024-28872?
No fix has been published for CVE-2024-28872 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-28872 being exploited?
There is no known exploitation of CVE-2024-28872 in the wild and no public exploit code.
Sources
Also known as GHSA-cvcp-p7f2-2rhw.