Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-28872Incorrect 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.

Timeline

  1. ID reserved

    By isc

  2. · 4 months later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-28872, by who scored it
Scored byCVSSScoreVector
iscCNA (assigner)3.1High8.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H
NVDNVD · Modified3.1High8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

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

References1

Sources

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

Badge for a README or a ticket

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

Record last updated .