Unauthenticated service control via CA-signed agent certificate
Published Jul 11, 2024 · Updated Mar 26, 2025
Improper certificate validation in ISC Stork 0.15.0 through 1.15.0 allows remote attackers to control monitored services. The server signs an attacker-submitted agent CSR, while agents accept any certificate from that CA without verifying that the peer is the registered Stork server. Network access to the server and an agent is required; successful abuse can read confidential Kea or BIND 9 data, change configurations, or shut down the agent or monitored service.
Summary
What happened
Improper certificate validation in ISC Stork 0.15.0 through 1.15.0 allows remote attackers to control monitored services. The server signs an attacker-submitted agent CSR, while agents accept any certificate from that CA without verifying that the peer is the registered Stork server. Network access to the server and an agent is required; successful abuse can read confidential Kea or BIND 9 data, change configurations, or shut down the agent or monitored service.
The record
- CVE
- CVE-2024-28872
- Published
- Jul 11, 2024
- Updated
- Mar 26, 2025
- Vendor
- Internet Systems Consortium
- Product
- Stork
- Classifications
- CWE-295, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.15.0 <=1.15.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo