From 1f1d83c824f188ef1aa71f9a591aefebb3f3d58b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Krzysztof=20Zaj=C4=85c?= Date: Wed, 16 Aug 2023 13:40:32 +0200 Subject: [PATCH] AWS metadata description informs that it could be other cloud provider --- http/misconfiguration/proxy/metadata-aws.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/http/misconfiguration/proxy/metadata-aws.yaml b/http/misconfiguration/proxy/metadata-aws.yaml index 2a6e4a96cd..900b74afdd 100644 --- a/http/misconfiguration/proxy/metadata-aws.yaml +++ b/http/misconfiguration/proxy/metadata-aws.yaml @@ -12,7 +12,7 @@ info: name: Amazon AWS Metadata Service Check author: sullo,DhiyaneshDk severity: critical - description: The AWS host is configured as a proxy which allows access to the metadata service. This could allow significant access to the host/infrastructure. + description: The host is configured as a proxy which allows access to the metadata provided by a cloud provider such as AWS or OVH. This could allow significant access to the host/infrastructure. reference: - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html - https://blog.projectdiscovery.io/abusing-reverse-proxies-metadata/