developmentseed / developmentseed/titiler-lambda-layer

Security Concern: Unrestricted S3 Access in Titiler Policy

Open
#40 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
17
Forks
4
PR merge metrics
No merged PRs in 30d

Description

The CloudFormation template ([sam.yml](https://github.com/developmentseed/titiler-lambda-layer/blob/main/sam.yml)) you provided grants the Lambda function [unrestricted access to all S3 buckets](https://github.com/developmentseed/titiler-lambda-layer/blob/main/sam.yml?plain=1#L57) through the policy associated with the [AWSLambdaExecute](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSLambdaExecute.html) statement. This presents a significant security risk, as the application might unintentionally access or modify data in buckets unrelated to its intended operations. This could potentially expose sensitive information or disrupt critical business processes.
- Recommendations:
1) Refactor the policy: Use a least privilege approach by specifying the exact S3 buckets the function requires access to instead of using wildcards (*).
2) Consider IAM roles: Utilize IAM roles to grant specific permissions to the Lambda function instead of relying on the broader AWSLambdaExecute policy.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.