Merge pull request #152 from MettleSphee/patch-1

Repaired Images

content/HackTheVote_2024/The Thirty-Twodle Challenge.md

@@ -33,7 +33,7 @@ But don't worry, it's not *that* hard. This game has some specific caveats:
 - You have 37 guesses to find all the words;
 
 That's a lot of information. Okay, so that means we just have to input all words and we win, right?
-![[wordle1.png]]
+![[/images/HackTheVote_2024/wordle1.png]]
 Guess not. By looking through the code, it gives access to ``/bin/sh`` only when (simplified) all words are auto-solved. Given that it adds a guess whenever it auto-solves a word, we basically have 37 - 32 = 5 guesses which we can use to add words that contribute to auto-solving. How do we do that?
 
 We can extract the full wordlist from the binary, and we can get the solution for that seed. As it turns out, finding the right words to auto-solve for a specific seed *may* be difficult. Factors which include having too many letters. As we have only 5 guesses with 5 letters each, that means a total of 25 letters. Given that we don't have many vowels, or other characters that repeat more often than not, we're going to have to find a good seed. The words are taken in a pseudo-random order from the wordlist using libc's ``srand(seed)`` function.
@@ -51,9 +51,9 @@ While doing all of this, I decided to keep the script running for the lulz to se
 
 
 After lots of trial and error due to some seeds being too difficult during testing, the scripts were ready. All that was left to do was to test the found words and get the flag:
-![[wordle2.png]]
+![[/images/HackTheVote_2024/wordle2.png]]
 After we got the flag, I wanted to combine all scripts into a singular one for solving to make it slightly more clean.
-![[wordle_solve.png]]
+![[/images/HackTheVote_2024/wordle_solve.png]]
 ## Flag
 ``flag{my_opening_words_are_stare_and_doing_wbu}``
 ## Appendix