does this actually result in any vulnerability? If not, I feel like this
is the wrong place for posting “bug reports”. If this leads to security
issues, some sort of PoC would be interesting.
You also might consider to publish a *generic* advisory for your
innosetup related findings. I do not see any additional information for
the specific targets. It seems to be the very same finding for each
advisory.
InnoSetup is BROKEN, it creates DEFECTIVE “portable executable”
image files, for example innosetup-5.5.9.exe itself.
JFTR: unfortunately Windows’ module loader covers these bugs and
loads such defective PE image files.
DEFECTS:
~~~~~~~~
1. all (8) IMAGE_IMPORT_DESCRIPTOR entries in the IMPORT directory
are INVALID: their Characteristics/OriginalFirstThunk fields
contain 0 instead of the RVA of the import…
I’m speechless, and almost don’t know what I should write… I (hardly) can’t believe what I have just found.
I have just discovered (to what I strongly believe is backdoor) in Dahua DVR/NVR/IPC and possible all their clones.
Since I am convinced this is a backdoor, I have my own policy to NOT notify the vendor before the community.
(I simply don’t want to listen on their poor excuses, their tryings to keep me silent…