CVE-2025-3047: Path Traversal in AWS SAM CLI allows file copy to build container
Summary
The AWS Serverless Application Model Command Line Interface (AWS SAM CLI) is an open-source CLI tool that helps Lambda developers to build and develop Lambda applications locally on their computers using Docker.
When running the AWS SAM CLI build process with Docker and symlinks are included in the build files, the container environment allows a user to access privileged files on the host by leveraging the elevated permissions granted to the tool. A user could leverage the elevated permissions to access restricted files via symlinks and copy them to a more permissive location on the container.
Users should upgrade to v1.133.0 or newer and ensure any forked or derivative code is patched to incorporate the new fixes.
Impact
This issue is limited to the local workspace and does not affect AWS services, production environments or cross-account resources. The issue only affects local workspaces using AWS SAM CLI with container builds (--use-container), potentially allowing access to local files outside the build directory through the usage of symlinks.
Impacted versions: <= AWS SAM CLI v1.132.0
Patches
The issue has been addressed in version 1.133.0. Users should upgrade and ensure any forked or derivative code is patched to incorporate the new fixes. To retain the previous behavior and allow symlinks to resolve on the host machine, please use the explicit '--mount-symlinks' parameter.
Workarounds
There is no recommended work around. Customers are advised to upgrade to version v1.133.0 or the latest version.
References
CVE-2025-3047
---
If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Credit
We would like to thank Kevin Backhouse with the GitHub Security Lab for collaborating on this issue through the coordinated vulnerability disclosure process.
Other sources
When running the AWS Serverless Application Model Command Line Interface (SAM CLI) build process with Docker and symlinks are included in the build files, the container environment allows a user to access privileged files on the host by leveraging the elevated permissions granted to the tool. A user could leverage the elevated permissions to access restricted files via symlinks and copy them to a more permissive location on the container.
Users should upgrade to v1.133.0 or newer and ensure any forked or derivative code is patched to incorporate the new fixes.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-3047?
CVE-2025-3047 is classified as a high-severity vulnerability due to the risk of unauthorized access to privileged files on the host.
How do I fix CVE-2025-3047?
To fix CVE-2025-3047, update the AWS Serverless Application Model CLI to a version higher than 1.133.0.
What versions of AWS Serverless Application Model CLI are affected by CVE-2025-3047?
CVE-2025-3047 affects AWS Serverless Application Model CLI versions up to 1.133.0.
What kind of access does CVE-2025-3047 allow attackers?
CVE-2025-3047 allows attackers to access privileged files on the host system by leveraging elevated permissions granted to the Docker container.
Is CVE-2025-3047 specific to certain environments?
Yes, CVE-2025-3047 specifically affects scenarios where the AWS SAM CLI build process is conducted with Docker and involves symlinked files.