Kiro Cli
Monthly
Uncontrolled search path execution in Amazon Kiro CLI on Windows allows arbitrary code execution when a local user opens the CLI within a maliciously crafted project directory. Affected versions are all Kiro CLI releases before 2.10.0 on Windows; the flaw bypasses workspace trust protections by placing a malicious executable in a directory that Kiro CLI resolves via an uncontrolled search path. No public exploit code has been identified at time of analysis, though exploitation requires only user interaction - not attacker presence on the system - making social engineering a viable delivery mechanism.
Authorization bypass in AWS Kiro CLI versions prior to 1.28.0 allows a local attacker to invoke arbitrary tools, including shell commands, without triggering the user approval prompt by piping crafted content through stdin. Reported by Amazon (AMZN) and tagged as an Authentication Bypass, this issue has a vendor-released fix in 1.28.0; publicly available exploit code exists is not indicated, and the SSVC framework currently records no observed exploitation despite a Total technical impact rating.
Uncontrolled search path execution in Amazon Kiro CLI on Windows allows arbitrary code execution when a local user opens the CLI within a maliciously crafted project directory. Affected versions are all Kiro CLI releases before 2.10.0 on Windows; the flaw bypasses workspace trust protections by placing a malicious executable in a directory that Kiro CLI resolves via an uncontrolled search path. No public exploit code has been identified at time of analysis, though exploitation requires only user interaction - not attacker presence on the system - making social engineering a viable delivery mechanism.
Authorization bypass in AWS Kiro CLI versions prior to 1.28.0 allows a local attacker to invoke arbitrary tools, including shell commands, without triggering the user approval prompt by piping crafted content through stdin. Reported by Amazon (AMZN) and tagged as an Authentication Bypass, this issue has a vendor-released fix in 1.28.0; publicly available exploit code exists is not indicated, and the SSVC framework currently records no observed exploitation despite a Total technical impact rating.