-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support IMDSv2 for AWS authentication #2482
Comments
@tsandall happy to! |
@tsandall @patrick-east I think the linked PR covers the requirement - let me know what you think. |
patrick-east
pushed a commit
that referenced
this issue
Jun 26, 2020
Fixes: #2482 Signed-off-by: Nick Williams <nhw@me.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The original AWS instance metadata service that is used in OPA (IMDSv1) is vulnerable to SSRF attacks, whereby an attacker uses a misconfigured WAF/upload capability/etc. to disclose the credentials inappropriately. This vulnerability is known to have been involved in significant attacks on AWS-hosted applications.
In many environments, adoption of IMDSv2 (which is session-based vs. request/response for v1) is becoming mandatory as technology risk functions look to minimize the vulnerability surface.
Since OPA depends on a bespoke implementation of IMDSv1 for AWS credential management, that implementation will need to be upgraded for IMDSv2, rather than benefiting automatically through SDK integration.
ref. also #1340 and #1600 for more discussion of the cost/benefit of this integration approach
The text was updated successfully, but these errors were encountered: