3 ms·
To be honest, I'm not so sure about that. Two attack surfaces I can think of off the top of my head where that could be leveraged are dynamic plugin loading, a
by vetrom 12y ago
To be honest, I'm not so sure about that. Two attack surfaces I can think of off the top of my head where that could be leveraged are dynamic plugin loading, a-la old school ActiveX, and LD_LIBRARY_PATH attacks on ld.so based platforms.
One might say that both of these vectors are obsolete, but anytime you have a dynamic coding situation, that is one more term which is added to the equation of how one can interact with a system, regardless of its legitimacy.
I'm reminded of this example: http://archive09.linux.com/feature/42031 http://archive09.linux.com/feature/42031
Or perhaps another example involving attacks which use many vectors, a dual action bytecode verifier & x86 shellcode attack:
http://www.securityfocus.com/blogs/746 http://www.securityfocus.com/blogs/746
If you can convince any piece of code to do the unintended, that can be a constructive attack vector. Sure, we can harken back to the old days when code only did simple parsing and stayed away from data parsed in multiple contexts. I doubt that will be a sellable market proposition in the age of the Internet of Advertising, however!
- phaedrus 12y agoI think you are confused between what linking and DLL loading are. They are different things. Linking is a step done during program development on object code by a compiler toolchain program to produce an executable. DLL loading is a step done by the OS on a user's machine at runtime to load an executable. Most non-developer Windows user machines will not even have a linker installed on the system.