aws/agent-toolkit-for-aws processing-s3-uploads-with-step-functions
Checked the catalogued skill at processing-s3-uploads-with-step-functions.
C; retained sample includes a medium finding · SD-008 · what this rule accepts as a false positive →
A set by no findings on this axis
A set by no findings on this axis
12 suppressed by AI triage
The absolute path /tmp/lambda_function.zip is used only in instructional shell commands for packaging and is not executed automatically.
The absolute path /tmp/statemachine.asl.json is referenced in a command shown to the user and not used by code, so it poses no threat.
The script writes a temporary file to /tmp/small-file.txt as part of a usage example; this is harmless and expected.
Same as finding 3; the reference is part of instructional text and not exploitable.
Documentation shows benign use of /tmp for temporary files.
Illustrates temporary file creation, not malicious path traversal.
Temporary file usage in examples; no real traversal.
Documentation example; no harmful path access.
Absolute path /tmp is inside the container filesystem, a common safe practice; no traversal of host files.
Pip install from /tmp/requirements.txt inside the container is safe; it does not access host system files.
The path uses /tmp with os.path.basename to prevent traversal, which is a safe temp location in Fargate
The use of /tmp for temporary storage in Lambda is expected and not a path traversal risk.