Skip to content

AWS Simple EC2 CLI does not explicitly validate AMI owner

Low
LikithaVemulapalli published GHSA-fg2w-j28v-fc73 Feb 7, 2025

Package

gomod aws-simple-ec2-cli (Go)

Affected versions

<= v0.10.0

Patched versions

v0.11.0

Description

Summary

AWS Simple EC2 is a CLI tool that combines the process of launching, connecting, and terminating EC2 instances into a single command for ad hoc testing.

In versions of <= v0.10.0, during AMI selection, AMI filtering validates the AMI name only. The lack of explicit AMI owner validation is inconsistent with public EC2 documentation and guidelines. Accurate discovery and selection of a necessary AMI requires owner specification and / or filtering.

Impact

A user may unintentionally launch an EC2 instance of an AMI of matching name from an untrusted publisher, potentially resulting in availability or other security concerns as a result of executing incorrect or malicious software.

Impacted Versions: <= v0.10.0

Patches

A patch for the issue is available for versions v0.11.0 and above. The patch uses the owner-alias field of AMI in the filtering logic, which is a common validation to mitigate the concern.

Credits

We would like to thank Seth Art, GH alias: @sethsec for reporting this issue.

If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our reporting page [1] or directly via email to [email protected]. Please do not create a public GitHub issue.

[1] Reporting page: https://aws.amazon.com/security/issue-reporting

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

CVE ID

No known CVE

Weaknesses

No CWEs

Credits