Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
The AWS Command Line Interface (AWS CLI) is a unified tool to manage AWS services from the command line. An issue exists where the EMR SSH helper commands (aws emr ssh, aws emr socks, aws emr put, aws emr get) passed StrictHostKeyChecking=no to the underlying SSH client, disabling host key verification. Impact A network-positioned actor could perform a man-in-the-middle action to intercept SSH sessions and file transfers between the client and EMR cluster instances. Successful exploitation requires the actor to have network access on the path between the client machine and the EMR cluster endpoint. This could result in full visibility of commands executed, files transferred, and credentials passed over the SSH session. Impacted versions: AWS CLI v1 <= 1.45.27, AWS CLI v2 <= 2.35.2 Patches This issue has been addressed in AWS CLI v1 version 1.45.28 and AWS CLI v2 version 2.35.3. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched…
Recommended action: Upgrade to 1.45.28 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The AWS Command Line Interface (AWS CLI) is a unified tool for managing AWS services from the command line. Certain CLI subcommands wrote credential and configuration files with world-readable permissions on Unix-like systems with a default umask, allowing other local users on the same host to read credentials. Impact On Unix-like systems with a default umask, the following AWS CLI subcommands wrote credential or configuration files with world-readable permissions (0644) instead of owner-only (0600): - aws codeartifact login - aws iam create-virtual-mfa-device - aws deploy register Any other local user on the same host could read these files and obtain the credentials. Impacted versions: <=1.44.77 (v1) AND <=2.34.28 (v2) Patches This issue has been addressed in AWS CLI v1 version 1.44.78 and AWS CLI v2 version 2.34.29. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. If you have any questions or…
Recommended action: Upgrade to 1.44.78 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
AWS CLI is a command line tool for interacting with AWS services. When the clihistory feature is enabled, the history database file is created with default permissions, potentially allowing other local users on a multi-user system to read the file. Impact When clihistory is enabled, AWS CLI stores command history including command parameters and API request/response data in a local SQLite database. On multi-user Unix systems, the default file permissions may allow other local users to read this file, potentially exposing sensitive information. This issue only affects users who have explicitly enabled clihistory, which is disabled by default. Impacted versions: 1.13.0 - 1.44.37 (v1), 2.0.0 - 2.33.20 (v2) Patches This issue has been addressed in the latest versions 2.33.21 and 1.44.38 of AWS CLI. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Workarounds Users can manually set restrictive…
Recommended action: Upgrade to 1.44.38 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.