Merge pull request #7569 from projectdiscovery/SSRF-Payload-Addition

Update metadata-aws.yaml

http/misconfiguration/proxy/metadata-aws.yaml

@@ -10,13 +10,15 @@ id: metadata-service-aws
 
 info:
   name: Amazon AWS Metadata Service Check
-  author: sullo
+  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.
   reference:
     - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
     - https://blog.projectdiscovery.io/abusing-reverse-proxies-metadata/
     - https://www.mcafee.com/blogs/enterprise/cloud-security/how-an-attacker-could-use-instance-metadata-to-breach-your-app-in-aws/
+    - https://twitter.com/Random_Robbie/status/1268186743657947137
+    - https://github.com/swisskyrepo/PayloadsAllTheThings/tree/master/Server%20Side%20Request%20Forgery#
   classification:
     cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
     cvss-score: 9.3
@@ -36,6 +38,8 @@ http:
       hostval:
         - aws.oast.online
         - 169.254.169.254
+        - 2852039166 # decimal encoding
+        - 169.254.169.254.nip.io
     unsafe: true
     matchers:
       - type: word
@@ -44,5 +48,4 @@ http:
           - "public-ipv4"
           - "privateIp"
         condition: or
-
 # Enhanced by mp on 2022/04/22