What is the severity of CVE-2018-15869?

CVE-2018-15869 is considered a moderate severity vulnerability due to the potential risk of deploying malicious Amazon Machine Images.

How do I fix CVE-2018-15869?

To mitigate CVE-2018-15869, ensure that you always specify the --owners flag when using the AWS CLI to describe images.

What impact does CVE-2018-15869 have on AWS environments?

CVE-2018-15869 can potentially lead to the deployment of unauthorized and harmful AMIs, affecting the security of your AWS environment.

Who is affected by CVE-2018-15869?

Developers and users of HashiCorp Packer prior to version 1.3.0 who utilize the AWS CLI without proper flags are at risk from CVE-2018-15869.

Is it safe to use HashiCorp Packer with AWS if CVE-2018-15869 is present?

Using HashiCorp Packer with AWS without mitigation for CVE-2018-15869 can expose your environment to risks from malicious AMIs.

Vulnerability/
CVE-2018-15869

medium

5.3

CWE

732

25/8/2018

5/8/2024

CVE-2018-15869

First published: Sat Aug 25 2018(Updated: )

An Amazon Web Services (AWS) developer who does not specify the --owners flag when describing images via AWS CLI, and therefore not properly validating source software per AWS recommended security best practices, may unintentionally load an undesired and potentially malicious Amazon Machine Image (AMI) from the uncurated public community AMI catalog.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Hashicorp Packer	<1.3.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-15869?
CVE-2018-15869 is considered a moderate severity vulnerability due to the potential risk of deploying malicious Amazon Machine Images.
How do I fix CVE-2018-15869?
To mitigate CVE-2018-15869, ensure that you always specify the --owners flag when using the AWS CLI to describe images.
What impact does CVE-2018-15869 have on AWS environments?
CVE-2018-15869 can potentially lead to the deployment of unauthorized and harmful AMIs, affecting the security of your AWS environment.
Who is affected by CVE-2018-15869?
Developers and users of HashiCorp Packer prior to version 1.3.0 who utilize the AWS CLI without proper flags are at risk from CVE-2018-15869.
Is it safe to use HashiCorp Packer with AWS if CVE-2018-15869 is present?
Using HashiCorp Packer with AWS without mitigation for CVE-2018-15869 can expose your environment to risks from malicious AMIs.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/first-publish-date
agent/description
agent/author
agent/event
agent/tags
agent/source
vendor/hashicorp
canonical/hashicorp packer

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-15869?
CVE-2018-15869 is considered a moderate severity vulnerability due to the potential risk of deploying malicious Amazon Machine Images.
How do I fix CVE-2018-15869?
To mitigate CVE-2018-15869, ensure that you always specify the --owners flag when using the AWS CLI to describe images.
What impact does CVE-2018-15869 have on AWS environments?
CVE-2018-15869 can potentially lead to the deployment of unauthorized and harmful AMIs, affecting the security of your AWS environment.
Who is affected by CVE-2018-15869?
Developers and users of HashiCorp Packer prior to version 1.3.0 who utilize the AWS CLI without proper flags are at risk from CVE-2018-15869.
Is it safe to use HashiCorp Packer with AWS if CVE-2018-15869 is present?
Using HashiCorp Packer with AWS without mitigation for CVE-2018-15869 can expose your environment to risks from malicious AMIs.