search

microsoft / binskim

A binary static analysis tool that provides security and correctness results for Windows Portable Executable and *nix ELF binary formats
Other
780 stars 156 forks source link

BinSkim cannot load PDBs for ildasm.exe even though they are present on Mcirosofts symbols servers #92

Open DkSkydancer opened 7 years ago

DkSkydancer commented 7 years ago

Hi

I am unable to implement BinSkim of my projects build output, because among the files it produces on our drop server, ildasm.exe is found. BinSkim issues an ExceptionLoadingPdb error:

binskim analyze ildasm.exe --sympath SRV*http://msdl.microsoft.com/download/symbols -v Analyzing... Analyzing 'ildasm.exe'... [...] error ERR997.ExceptionLoadingPdb : BA2006 : 'ildasm.exe' was not evaluated for check 'BuildWithSecureTools' because its PDB could not be loaded. (E_PDB_NOT_FOUND (File not found)) [...]

One or more rules was disabled for an analysis target, as it was determined not to be applicable to it (this is a common condition). Pass --verbose on the command-line for more information.

Analysis did not complete due to one or more unrecoverable execution conditions. Unexpected fatal runtime condition(s) observed: ExceptionLoadingPdb

I am able toto verify the binaries can be dfoudn on teh server e:\rainfnd>\symbols\tools\x86\symchk.exe Source\Servicing\AXCreateDeployablePackageTool\AXCreateDeployablePackageBase\ildasm.exe /s SRV*http://msdl.microsoft.com/download/symbols /od SYMCHK: ildasm.exe PASSED - PDB: ildasm.pdb DBG: <N/A>

SYMCHK: FAILED files = 0 SYMCHK: PASSED + IGNORED files = 1

What can I do to get BinSkim to find the symbols?

Thanks Bo

michaelcfanning commented 7 years ago

Hm. --sympath SRV*http://msdl.microsoft.com/download/symbols is working fine for other files in my testing, such as kernel32.dll. Will take a closer look at ildasm.exe test case.

Evmaus-MS commented 6 years ago

@michaelcfanning Did this ever get investigated/resolved?

michaelcfanning commented 6 years ago

not completely. we should try to reproduce the symchk.exe test. any underlying problem is likely to resolve to our symsrv.dll or a problem on the symbol server itself.