CVE-2024-28872 - CVE House
Back to Database
Status published High CVE-2024-28872

Incorrect TLS certificate validation can lead to escalated privileges

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2024-28872

Credits & Attribution

No credits recorded in the NVD database.

References

More from ISC

View All →
CVE-2025-8696
DoS attack against the Stork UI from an unauthenticated user
High 7.5
CVE-2025-8677
Resource exhaustion via malformed DNSKEY handling
High 7.5
CVE-2025-40780
Cache poisoning due to weak PRNG
High 8.6
CVE-2025-40779
Kea crash upon interaction between specific client options and subnet selection
High 7.5
CVE-2025-40778
Cache poisoning attacks with unsolicited RRs
High 8.6

Affected Vendor

Affected Software

Stork
Vulnerable Versions:
0.15.0

Timeline

Official Publish: July 11th, 2024
Last Modified: March 26th, 2025
Added to House: July 22nd, 2026

CVSS Vectors

V3: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.