[SERVER-45241] Use instance metadata service v2 instead of v1 Created: 18/Dec/19  Updated: 29/Oct/23  Resolved: 02/Jan/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Bug Priority: Major - P3
Reporter: Mark Benvenuto Assignee: Mark Benvenuto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Security 2019-01-13
Participants:

 Description   

On Nov 19, 2019, AWS announced a new IMDSv2 which is more secure then IMDSv1. The shell should be updated to use IMDSv2 instead of IMDSv1.

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

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html



 Comments   
Comment by Githook User [ 02/Jan/20 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-45241 Use instance metadata service v2 instead of v1
Branch: master
https://github.com/mongodb/mongo/commit/87f947409fdd0074acf4c8301355dabe4d4098f9

Comment by Githook User [ 02/Jan/20 ]

Author:

{'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}

Message: SERVER-45241 Use instance metadata service v2 instead of v1
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/1ffab8d6319a81979f95e55b068b7a73972d3768

Generated at Thu Feb 08 05:08:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.