bluehammer vulnerability
Go to file
2026-06-10 00:56:18 +00:00
FunnyApp.aps Upload files to "/" 2026-06-10 00:55:27 +00:00
FunnyApp.cpp Upload files to "/" 2026-06-10 00:55:27 +00:00
FunnyApp.rc Upload files to "/" 2026-06-10 00:55:27 +00:00
FunnyApp.sln Upload files to "/" 2026-06-10 00:55:37 +00:00
FunnyApp.vcxproj Upload files to "/" 2026-06-10 00:55:37 +00:00
FunnyApp.vcxproj.filters Upload files to "/" 2026-06-10 00:55:37 +00:00
FunnyApp.vcxproj.user Upload files to "/" 2026-06-10 00:55:59 +00:00
LICENSE Upload files to "/" 2026-06-10 00:55:59 +00:00
offreg.h Upload files to "/" 2026-06-10 00:55:59 +00:00
offreg.lib Upload files to "/" 2026-06-10 00:56:08 +00:00
README.md Upload files to "/" 2026-06-10 00:56:08 +00:00
resource.h Upload files to "/" 2026-06-10 00:56:08 +00:00
windefend_c.c Upload files to "/" 2026-06-10 00:56:18 +00:00
windefend_h.h Upload files to "/" 2026-06-10 00:56:18 +00:00
windefend_s.c Upload files to "/" 2026-06-10 00:56:18 +00:00
windefend.idl Upload files to "/" 2026-06-10 00:56:18 +00:00

BlueHammer

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

Repository hosting the bluehammer vulnerability

I'm just really wondering what was the math behind their decision, like you knew this was going to happen and you still did whatever you did ? Are they serious ?

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRJTvAf/AWVhAKEeb7FFoRCS0/SbAUCac8VlgAKCRDFFoRCS0/S bK8pAP9CzNnH26FVVdHZWVyDvOIwuZ1np1dTv7T5YaVCjf4tiwD+MC4Ikq+/ywdD I7dabkH7iSZflULM+hGUOur0mnAg9Qw= =Enhh -----END PGP SIGNATURE-----

Edit : There are few bugs in the PoC that could prevent it from working, might fix them later.