{"answers":{"affected":"2 open source packages ship an affected version, including aws-sam-cli.","exploited":"There is no known exploitation of GHSA-rjc6-vm4h-85cg in the wild and no public exploit code.","fix":"Upgrade aws-sam-cli to 1.122.0 or later.","what":"GHSA-rjc6-vm4h-85cg is a vulnerability in aws-sam-cli, published on 11 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-rjc6-vm4h-85cg and fix it if it is affected.\n\nWhat it is: GHSA-rjc6-vm4h-85cg is a vulnerability in aws-sam-cli, published on 11 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-rjc6-vm4h-85cg in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aws-sam-cli (PyPI): affected all versions; fixed in 1.122.0\n- aws-sam-cli (PyPI): affected all versions; fixed in 1.122.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-rjc6-vm4h-85cg/ (Markdown: https://insights.sbomify.com/GHSA-rjc6-vm4h-85cg/index.md)","id":"GHSA-rjc6-vm4h-85cg","markdown":"https://insights.sbomify.com/GHSA-rjc6-vm4h-85cg/index.md","name":"GHSA-rjc6-vm4h-85cg","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"AWS SAM CLI","requires_auth":"none","summary":"AWS SAM CLI exposes sensitive Docker build arguments in clear text logs, allowing local attackers to read secrets if specific parameters are used.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nThe AWS Serverless Application Model (SAM) CLI is an open source tool that allows customers to build, deploy and test their serverless applications built on AWS. AWS SAM CLI can build container (Docker) images and customers can specify arguments in the SAM template that are passed to the Docker engine during build [1].\n\n### Impact\nIf customers specify sensitive data in the DockerBuildArgs parameter of their template, the sensitive data will be shown in clear text in the AWS SAM CLI output via STDERR  when running the sam build command.\n\n### Patches\nA patch is included in aws-sam-cli\u003e=1.122.0.\n\nWe strongly recommend customers install AWS SAM CLI v1.122.0 or above. Please review logs produced by your SAM CLI runs if you have used the DockerBuildArgs parameter and consider rotating the secrets if you believe they were exposed.\n\n### References\nIf you have any questions or comments about this issue, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.\n\n[1] https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-build.html#build-container-image \n\n[2] https://aws.amazon.com/security/vulnerability-reporting","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Sensitive Information Exposure Through Insecure Logging For Secrets Like Metadata.DockerBuildArgs","id":"GHSA-rjc6-vm4h-85cg","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":["1.122.0"],"introduced":["0"],"last_affected":[],"package":"aws-sam-cli","purl":null,"source":"GHSA-rjc6-vm4h-85cg"},{"ecosystem":"PyPI","fixed":["1.122.0"],"introduced":["0"],"last_affected":[],"package":"aws-sam-cli","purl":"pkg:pypi/aws-sam-cli","source":"GHSA-rjc6-vm4h-85cg"}],"products":null,"published":"2024-09-11","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"AWS SAM CLI exposes sensitive Docker build arguments in clear text logs, allowing local attackers to read secrets if specific parameters are used.","url":"https://insights.sbomify.com/GHSA-rjc6-vm4h-85cg/"}