CyberRota Analysis
AI-GeneratedThe vulnerability affects the kas setup tool for bitbake projects, where improper handling of SSH key configurations can lead to the creation of a global SSH configuration that disables host key verification. This flaw allows subsequent SSH connections to accept unverified host keys, increasing the risk of man-in-the-middle attacks that can compromise session confidentiality and integrity. Organizations using versions prior to 5.4 should prioritize upgrading to mitigate potential security risks associated with this configuration issue.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.