CVE-2024-28872: Incorrect TLS certificate validation can lead to escalated privileges
First published: Thu Jul 11 2024(Updated: )
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.
Credit: security-officer@isc.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Isc Stork | >=0.15.0<1.15.1 |
Remedy
Upgrade to the patched release most closely related to your current version of Stork: 1.15.1.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/title
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/event
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/isc
- canonical/isc stork
- version/isc stork/0.15.0