From df571e5ee76954f501c6329380d44dd6acc8e2ab Mon Sep 17 00:00:00 2001 From: "Florine W. Dekker" Date: Sat, 20 Aug 2022 14:10:59 +0200 Subject: [PATCH] Remove unexpected HTML element --- 2021/docs/A10_2021-Server-Side_Request_Forgery_(SSRF).md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2021/docs/A10_2021-Server-Side_Request_Forgery_(SSRF).md b/2021/docs/A10_2021-Server-Side_Request_Forgery_(SSRF).md index 11dfbb812..515ff060b 100644 --- a/2021/docs/A10_2021-Server-Side_Request_Forgery_(SSRF).md +++ b/2021/docs/A10_2021-Server-Side_Request_Forgery_(SSRF).md @@ -84,7 +84,7 @@ elapsed time to connect or reject SSRF payload connections. **Scenario #2:** Sensitive data exposure – Attackers can access local files or internal services to gain sensitive information such -as `file:///etc/passwd` and `http://localhost:28017/`. +as `file:///etc/passwd` and `http://localhost:28017/`. **Scenario #3:** Access metadata storage of cloud services – Most cloud providers have metadata storage such as `http://169.254.169.254/`. An