Source code is a theoretical representation of what runs on your system. Compilers may add security boundaries, or (because you've accidentally triggered undefined behaviour in C) remove them. The binary is the only true representation of what's exploitable. Do we have any figures on whether analysis of source code is better or worse than analysis of the binary, especially if the binary is accompanied by debug symbols?
1 Boost
0 Likes
Yea, it's a boundary question on all layers.
Though this can easily "derail" the analysis.
What uarch, what microcode, what kernel/runtime, what did the firmware configure (myriads of MSRs or equivalent...) are all general factors.
This is the same as the question of what is needed for a bug reproducer. It can get pretty complex and complicated.
I take "given the source code", "given the binary", "given the binary and source", etc to imply the boundary considered.
@mjg59 The binary also might not tell the whole picture, as the various microarchitecture dependent speculative execution vulnerabilities that have come up in the last decade.