Challenge 20 ☆☆☆☆

Welcome to challenge 20. You need to guess the secret that is hidden in Java, Docker, Kubernetes, Vault, AWS or GCP.

Hiding in binaries part 2: the C++ binary

Similar like hiding secrets in an application written in C, you end up in a similar situation with C++. Can you find the secret in our binary?

Let’s debunk the "secrets are hard to find in native compiled applications" myth for C++: can you find the secret in wrongsecrets-cplus (or wrongsecrets-cplus-arm, wrongsecrets-cplus-linux)?

Answer to solution :

Why Using binaries to hide a secret will only delay an attacker.

With beautiful free Reverse engineering applications as Ghidra, not a lot of things remain safe. Anyone who can load the executable in Ghidra or Radare2 can easily start doing a reconnaissance and find secrets within your binary.

Encrypting the secret with a key embedded in the binary, and other funny puzzles do delay an attacker and just make it fun finding the secret. Be aware that, if the secret needs to be used by the executable, it eventually needs to be in memory ready to be executed.

Still need to have a secret in the binary? Make sure it can only be retrieved remotely after authenticating against a server.