Incorrect TLS certificate validation can lead to escalated privileges

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.

Scores

EPSS (exploitation in 30 days)

0.29% · top 78% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.9.

Weakness

• CWE-295 Improper Certificate Validation (opens in a new tab)All about CWE-295 and its CVEs

Affected products

• ISC · Stork

  • affected 0.15.0 – ≤ 1.15.0

What to do

Solution: Upgrade to the patched release most closely related to your current version of Stork: 1.15.1.

Workaround: It should be possible to decrease the attack vector by protecting the Stork server and Stork agents with a firewall or similar mechanism.

Exploitation: We are not aware of any active exploits.

References (1)

• CVE-2024-28872 (opens in a new tab)vendor-advisoryx_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-28872](https://trackcve.app/badge/CVE-2024-28872.svg)](https://trackcve.app/cve/CVE-2024-28872)

Record last updated 26 Mar 2025, 14:40 UTC.