Incorrect TLS certificate validation can lead to escalated privileges
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.
Metrics
| Version | Base score | Base severity | Vector |
|---|
| 3.1 | 8.9 | HIGH | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H |
Version: 3.1
Base score: 8.9
Base severity: HIGH
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H
Impacts
| CAPEC ID | Description |
|---|
| N/A | The possible impacts are denial of service, loss of confidential information, and integrity loss. If successful, the attacker can cause the Stork agent to shut down; the attacker can also obtain confidential data from Kea or BIND 9, cause those services to terminate, or modify their configurations. |
CAPEC ID: N/A
Description: The possible impacts are denial of service, loss of confidential information, and integrity loss. If successful, the attacker can cause the Stork agent to shut down; the attacker can also obtain confidential data from Kea or BIND 9, cause those services to terminate, or modify their configurations.