Incorrect default permissions on session transcripts and prompt history in Kiro CLI
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Amazon | Kiro CLI | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Amazon | Kiro Cli |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.109% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Incorrect default file permissions in Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and Linux might allow other local users on the same host to read a user's session transcripts and prompt history, including any credentials or source code they contain. The CLI created its local session storage files with permissions that made them readable by all local users. To remediate this issue, users should upgrade to Kiro CLI version 2.27.0 or later and launch it once. Users who ran Amazon Q Developer CLI 1.16.0 through 1.19.x should also delete the ~/.aws/amazonq/.cli_bash_history file or restrict it to the owner. | |
| Title | Incorrect default permissions on session transcripts and prompt history in Kiro CLI | |
| First Time appeared |
Amazon
Amazon kiro Cli |
|
| Weaknesses | CWE-276 | |
| CPEs | cpe:2.3:a:amazon:kiro_cli:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Amazon
Amazon kiro Cli |
|
| References |
| |
| Metrics |
cvssV3_1
|