Since you already know how to use GDB and you&#x27;re familiar with Assembly, Now i don&#x27;t know how much Assembly you know, but you need to know how programs execute in memory, (stack , heap , syscalls.....), and once you have that clear in your mind, try to draw a map  of thoughts about the logic of execution of this binary (it will be pretty simple, since it&#x27;s generally small programs), look for the points and weaknesses in the logic that you might attack, one tool i use frequently is [0]peda, also using some visual gdb extension would be really helpful for you instead of checking and looking every time on how registers change values, sometimes a little knowledge about how compilers work and the OS you&#x27;re working on will be really helpful although the binaries are independent in most cases, but extra knowledge is always useful.
[0]<a href="https:&#x2F;&#x2F;github.com&#x2F;longld&#x2F;peda" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;longld&#x2F;peda</a>