Kas
Monthly
SSH host key verification is persistently disabled in Siemens kas versions prior to 5.4 when the tool's internal SSH key setup path is triggered via SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE and the invoking user has no pre-existing ~/.ssh/config. The tool writes a global Host * rule with StrictHostKeyChecking no to ~/.ssh/config and does not remove it upon exit, leaving all subsequent SSH sessions of that local user silently accepting unverified host keys. No public exploit code exists and this vulnerability is not listed in CISA KEV; the low CVSS score of 3.3 correctly reflects a constrained local, multi-condition attack path, though the persistence of the misconfiguration indefinitely extends the exposure window beyond any single kas invocation.
SSH host key verification is persistently disabled in Siemens kas versions prior to 5.4 when the tool's internal SSH key setup path is triggered via SSH_PRIVATE_KEY or SSH_PRIVATE_KEY_FILE and the invoking user has no pre-existing ~/.ssh/config. The tool writes a global Host * rule with StrictHostKeyChecking no to ~/.ssh/config and does not remove it upon exit, leaving all subsequent SSH sessions of that local user silently accepting unverified host keys. No public exploit code exists and this vulnerability is not listed in CISA KEV; the low CVSS score of 3.3 correctly reflects a constrained local, multi-condition attack path, though the persistence of the misconfiguration indefinitely extends the exposure window beyond any single kas invocation.