Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copilot v1.34.0 (latest) is vulnerable to critical severity CVE-2024-24790 #6017

Closed
skylarmb opened this issue Mar 20, 2025 · 4 comments
Closed
Labels
type/bug Issues that are bugs.

Comments

@skylarmb
Copy link

skylarmb commented Mar 20, 2025

Description:

Amazon Inspector (and other automated vulnerability scanning tools) flag AWS Copilot v1.34.0 (latest available release at this time) as being vulnerable to CRITICAL severity 9.8 CVE-2024-24790.

Details:

AWS Copilot generated buildspec.yml files by default downloads the copilot-linux binary to the current working directory ./, which is also the root of the source code / repo for any docker image builds. This means when source code is copied into docker images e.g. COPY . ., unless manually ignored e.g. via .dockerignore etc, the copilot binary is also copied into all built images that are pushed to ECR.

This results in all images built / managed by AWS Copilot are detected by automated scanning tools such as AWS Inspector as being vulnerable to this critical CVE. This prevents an company using AWS Copilot from maintaining SOC 2 compliance, among other things.

Remediation suggestion:

  1. AWS Copilot needs a security patch release to address this vulnerability.
  2. AWS Copilot should by default generate a buildspec.yml file that does not inadvertently inject binaries into customers docker images, e.g. by simply downloading the binary to a different path on the filesystem instead of into the same directory as the application source code.
@skylarmb skylarmb added the type/bug Issues that are bugs. label Mar 20, 2025
@henry-hc
Copy link

The CoPilot Readme says to go here to report security issues (you can look at the readme for more details):
https://aws.amazon.com/security/vulnerability-reporting/

Just the messenger here. Not associated with AWS or anything like this.

@jlucas91
Copy link
Contributor

@bkaws @iamhopaul123 Sorry to tag individuals - hoping to get some visibility from the recent committers. I raised this to the vulnerability reporting email address, but haven't heard back. Could we get a canonical response from AWS on whether we can expect this (upgrading the go version, it seems?) to be within the scope of ongoing copilot-cli maintenance, or are we on our own here?

@bkaws
Copy link
Contributor

bkaws commented Apr 1, 2025

Hi @jlucas91 thank you for opening this issue and e-mailing the aws-security mailbox. We received your e-mail report and are looking into this.

@lucix-aws
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Issues that are bugs.
Projects
None yet
Development

No branches or pull requests

5 participants