kas: Persistent SSH Host Key Checking Disablement
Published Aug 26, 2026
3.3
LOWCVSS 3.1
EPSS 0.11%
Description
kas is a setup tool for bitbake based projects. Prior to 5.4, internal SSH key setup triggered by SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE creates ~/.ssh/config when no user-specific SSH configuration exists and adds a global Host * rule containing StrictHostKeyChecking no. In kas/libcmds.py, ssh_no_host_key_check() runs without checking ctx.managed_env, so the setting persists after kas exits and affects future SSH sessions by the same local user, extending beyond the intended short-lived continuous integration environment. A later SSH connection can therefore accept an attacker-controlled host key without verification, increasing the risk of a man-in-the-middle attack that compromises session confidentiality or integrity. This issue is fixed in version 5.4.
Affected products
-
- Version < 5.4StatusaffectedConstraints-
- Version
No data.
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
References (4)
- https://github.com/advisories/GHSA-mv8m-v9v6-5f94 Advisory
- https://github.com/siemens/kas/commit/1c1e861c9f241ce082b86bef6bedc7da9b676294 x_refsource_MISC
- https://github.com/siemens/kas/releases/tag/5.4 x_refsource_MISC
- https://github.com/siemens/kas/security/advisories/GHSA-mv8m-v9v6-5f94 x_refsource_CONFIRM
| Link | Providers | Tags |
|---|---|---|
| https://github.com/advisories/GHSA-mv8m-v9v6-5f94 | Advisory | |
| https://github.com/siemens/kas/commit/1c1e861c9f241ce082b86bef6bedc7da9b676294 | x_refsource_MISC | |
| https://github.com/siemens/kas/releases/tag/5.4 | x_refsource_MISC | |
| https://github.com/siemens/kas/security/advisories/GHSA-mv8m-v9v6-5f94 | x_refsource_CONFIRM |
Change history (0)
No recorded changes yet.