Vulnerability	Vulnerable Version
M Directory Traversal aws-sam-cli is an AWS SAM CLI is a CLI tool for local development and testing of Serverless applications Affected versions of this package are vulnerable to Directory Traversal due to the handling of symlinks during the build process. An attacker can access and copy restricted files to a more permissive location within the container by leveraging symlinks to bypass security restrictions. Note: The issue only affects local workspaces using AWS SAM CLI with container builds (--use-container). After upgrading to the fixed version and allowing symlinks to resolve on the host machine, users should use the explicit `--mount-symlinks` parameter. This is to retain the previous behavior. How to fix Directory Traversal? Upgrade `aws-sam-cli` to version 1.133.0 or higher.	[1.98.0,1.133.0)
M Directory Traversal aws-sam-cli is an AWS SAM CLI is a CLI tool for local development and testing of Serverless applications Affected versions of this package are vulnerable to Directory Traversal through the symlink handling process. After completing a build, the content of those symlinks is copied to the cache of the local workspace as regular files or directories, allowing an attacker who does not have access to those symlinks outside of the Docker container to get access via the local workspace. Note: After upgrading, users must re-build their applications using `sam build --use-container` to update the symlinks. How to fix Directory Traversal? Upgrade `aws-sam-cli` to version 1.134.0 or higher.	[1.9.0,1.134.0)

Directory Traversal

aws-sam-cli is an AWS SAM CLI is a CLI tool for local development and testing of Serverless applications

Affected versions of this package are vulnerable to Directory Traversal due to the handling of symlinks during the build process. An attacker can access and copy restricted files to a more permissive location within the container by leveraging symlinks to bypass security restrictions.

Note: The issue only affects local workspaces using AWS SAM CLI with container builds (--use-container).

After upgrading to the fixed version and allowing symlinks to resolve on the host machine, users should use the explicit --mount-symlinks parameter. This is to retain the previous behavior.

How to fix Directory Traversal?

Upgrade aws-sam-cli to version 1.133.0 or higher.

[1.98.0,1.133.0)

Directory Traversal

aws-sam-cli is an AWS SAM CLI is a CLI tool for local development and testing of Serverless applications

Affected versions of this package are vulnerable to Directory Traversal through the symlink handling process. After completing a build, the content of those symlinks is copied to the cache of the local workspace as regular files or directories, allowing an attacker who does not have access to those symlinks outside of the Docker container to get access via the local workspace.

Note: After upgrading, users must re-build their applications using sam build --use-container to update the symlinks.

How to fix Directory Traversal?

Upgrade aws-sam-cli to version 1.134.0 or higher.

[1.9.0,1.134.0)

Go back to all versions of this package