CVE-2024-28872
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Stork management tool has a flaw in its TLS certificate validation logic that allows an attacker who obtains a valid TLS certificate from the Stork server to impersonate that server and connect to Stork agents. Once authenticated with the stolen certificate, the attacker can send malicious commands to monitored Kea or BIND 9 services, potentially causing data exfiltration or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.15.0, < 1.15.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Stork installation and versionRun 'stork-server --version' or check the package manager for installed stork packages (e.g., 'dpkg -l | grep stork' or 'rpm -qa | grep stork')Affected if The installed version is >= 0.15.0 and < 1.15.1
-
Confirm Stork server is runningCheck for stork-server processes (e.g., 'ps aux | grep stork-server' or 'systemctl status stork-server')Affected if The Stork server process is running and the version meets the affected range condition
-
Verify TLS mutual authentication is enabledInspect Stork server configuration files for TLS/mTLS settings (commonly in /etc/stork/ or as indicated by documentation). Look for 'tls', 'cert', 'key', or 'mutual' configuration directivesAffected if TLS mutual authentication is configured between the Stork server and agents, making the certificate validation flaw applicable
You are affected if a Stork server is running with version 0.15.0 through 1.15.0 and TLS mutual authentication is enabled between the server and agents.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.15.1
Upgrade Stork to version 1.15.1 or later where the certificate validation vulnerability has been fixed. If immediate upgrade is not possible, review network access controls to limit exposure of the Stork server and agents to untrusted networks.
1.15.1
- Obtain Stork version 1.15.1 from official ISC sources (kb.isc.org or ISC's official download channels)
- Stop the currently running Stork server and agent services
- Back up the existing Stork configuration and database
- Install Stork version 1.15.1
- Start the Stork services
- Verify that TLS certificate validation is now working correctly by checking the TLS handshake and certificate verification logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28872 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28872 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data