From 13e64a1db7b3cccd7bd186fd6d6b9e6fb1a5b4c9 Mon Sep 17 00:00:00 2001 From: Maik de Kruif Date: Tue, 30 Mar 2021 21:27:01 +0200 Subject: [PATCH] Move image to challenge folder --- content/posts/adventofctf/challenge_16.md | 2 +- static/img/adventofctf/{ => 16}/ssti_graph.png | Bin 2 files changed, 1 insertion(+), 1 deletion(-) rename static/img/adventofctf/{ => 16}/ssti_graph.png (100%) diff --git a/content/posts/adventofctf/challenge_16.md b/content/posts/adventofctf/challenge_16.md index bb1e1af..309bf5d 100644 --- a/content/posts/adventofctf/challenge_16.md +++ b/content/posts/adventofctf/challenge_16.md @@ -56,7 +56,7 @@ SSTI occurs when an attacker is able to use native template syntax to inject a m An easy way to check for SSTI is by using the following graph from PortSwigger: -{{< figure src="/img/adventofctf/ssti_graph.png" title="SSTI Graph (by PortSwigger)" >}} +{{< figure src="/img/adventofctf/16/ssti_graph.png" title="SSTI Graph (by PortSwigger)" >}} So I followed this graph and got the following results: diff --git a/static/img/adventofctf/ssti_graph.png b/static/img/adventofctf/16/ssti_graph.png similarity index 100% rename from static/img/adventofctf/ssti_graph.png rename to static/img/adventofctf/16/ssti_graph.png