GitBook: [#3235] No subject

pentesting-web/ssrf-server-side-request-forgery/cloud-ssrf.md

@@ -107,7 +107,7 @@ Notice the **aws\_session\_token**, this is indispensable for the profile to wor
 **ECS**, is a logical group of EC2 instances on which you can run an application without having to scale your own cluster management infrastructure because ECS manages that for you. If you manage to compromise service running in **ECS**, the **metadata endpoints change**.
 
 If you access _**http://169.254.170.2/v2/credentials/\<GUID>**_ you will find the credentials of the ECS machine. But first you need to **find the \<GUID>**. To find the \<GUID> you need to read the **environ** variable **AWS\_CONTAINER\_CREDENTIALS\_RELATIVE\_URI** inside the machine.\
-You could be able to read it exploiting an **Path Traversal** to _file:///proc/self/environ_\
+You could be able to read it exploiting an **Path Traversal** to `file:///proc/self/environ`\
 The mentioned http address should give you the **AccessKey, SecretKey and token**.
 
 ```bash