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

Lacking IMDSv2 support #289

Open
phils opened this issue Feb 15, 2020 · 1 comment
Open

Lacking IMDSv2 support #289

phils opened this issue Feb 15, 2020 · 1 comment

Comments

@phils
Copy link

phils commented Feb 15, 2020

Issue type

  • Bug report

cli53 version (cli53 --version)

0.8.16

OS / Platform

Linux x64

Steps to reproduce

any cli53 command that does an AWS API call

Expected behaviour

IMDSv2 metadata service used

Actual behaviour

IMDSv1 metadata service used

Could you contribute a fix or help testing with this issue?

Fix is probably as simple as updating the AWS Go SDK to at least version v1.25.38 where support was added in November 2019.

Further background on IMDSv2:
https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/

@barnybug
Copy link
Owner

barnybug commented Mar 8, 2020

Please try the 0.8.17 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants