Incorrect TLS certificate validation can lead to escalated privileges
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| ISC | Stork | unaffected |
|
No data.
No data available yet.
Vendor Solution
Upgrade to the patched release most closely related to your current version of Stork: 1.15.1.
Vendor Workaround
It should be possible to decrease the attack vector by protecting the Stork server and Stork agents with a firewall or similar mechanism.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-25942 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.291% probability within 30 days)
| Link | Providers |
|---|---|
| https://kb.isc.org/docs/cve-2024-28872 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|