Cloud Metadata Potentially Exposed (From ZAP Scan)

[DmByK]

After Zap Scan one high-risk vulnerability was found

Description

The Cloud Metadata Attack attempts to abuse a misconfigured NGINX server in order to access the instance metadata maintained by cloud service providers such as AWS, GCP and Azure.

All of these providers provide metadata via an internal unroutable IP address '169.254.169.254' - this can be exposed by incorrectly configured NGINX servers and accessed by using this IP address in the Host header field.

URL http://localhost:4200/latest/meta-data/
Based on the successful response status code cloud metadata may have been returned in the response. Check the response data to see if any cloud metadata has been returned. The meta data returned can include information that would allow an attacker to completely compromise the system.

Solution
Do not trust any user data in NGINX configs. In this case it is probably the use of the $host variable which is set from the 'Host' header and can be controlled by an attacker.
Suggestion from StackHawk https://docs.stackhawk.com/vulnerabilities/90034/

Reference https://blog.nginx.org/blog/trust-no-one-perils-of-trusting-user-input