Article Details

Scrape Timestamp (UTC): 2024-04-16 13:29:40.983

Source: https://thehackernews.com/2024/04/aws-google-and-azure-cli-tools-could.html

Original Article Text

Click to Toggle View

AWS, Google, and Azure CLI Tools Could Leak Credentials in Build Logs. New cybersecurity research has found that command-line interface (CLI) tools from Amazon Web Services (AWS) and Google Cloud can expose sensitive credentials in build logs, posing significant risks to organizations. The vulnerability has been codenamed LeakyCLI by cloud security firm Orca. "Some commands on Azure CLI, AWS CLI, and Google Cloud CLI can expose sensitive information in the form of environment variables, which can be collected by adversaries when published by tools such as GitHub Actions," security researcher Roi Nisimi said in a report shared with The Hacker News. Microsoft has since addressed the issue as part of security updates released in November 2023, assigned it the CVE identifier CVE-2023-36052 (CVSS score: 8.6). The idea, in a nutshell, has to do with how the CLI commands such as could be used to show (pre-)defined environment variables and output to Continuous Integration and Continuous Deployment (CI/CD) logs. A list of such commands spanning AWS and Google Cloud is below 0 Orca said it found several projects on GitHub that inadvertently leaked access tokens and other sensitive data via Github Actions, CircleCI, TravisCI, and Cloud Build logs. Unlike Microsoft, however, both Amazon and Google consider this to be expected behavior, requiring that organizations take steps to avoid storing secrets in environment variables and instead use a dedicated secrets store service like AWS Secrets Manager or Google Cloud Secret Manager. Google also recommends the use of the "--no-user-output-enabled" option to suppress the printing of command output to standard output and standard error in the terminal. "If bad actors get their hands on these environment variables, this could potentially lead to view sensitive information including credentials, such as passwords, user names, and keys, which could allow them to access any resources that the repository owners can," Nisimi said. "CLI commands are by default assumed to be running in a secure environment, but coupled with CI/CD pipelines, they may pose a security threat." Goodbye, Atlassian Server. Goodbye… Backups? Protect your data on Atlassian Cloud from disaster with Rewind's daily backups and on-demand restores. How to Update and Automate Outdated Security Processes Download the eBook for step-by-step guidance on how to update your security processes as your business grows.

Daily Brief Summary

DATA BREACH // Vulnerability in CLI Tools Risks Exposing Credentials

Security flaw identified in AWS, Google Cloud, and Azure CLI tools could lead to credential leaks in build logs.

The issue has been given the identifier CVE-2023-36052 with a CVSS score of 8.6, indicating a high severity.

Microsoft addressed this vulnerability in their November 2023 security updates, but Google and Amazon have not released specific fixes.

The leaked data includes sensitive details like passwords and access tokens, directly threatening organizational cybersecurity.

Research by Orca highlights that several projects inadvertently exposed sensitive information on platforms like GitHub Actions and CircleCI.

Google and Amazon maintain that it is the responsibility of users to safeguard their environment variables and recommend using dedicated secrets management services.

The exposure is particularly concerning in Continuous Integration and Continuous Deployment (CI/CD) environments where CLI commands are commonly used.

Enhanced vigilance and security practices are advised for users to prevent potential data breaches and unauthorized access.